DeleteThreads

Like many indie developers, I tend to build tools to fix my own annoyances.

A few weeks ago, I decided I wanted a clean slate on Threads. New start, fresh profile.
Then I realized something surprisingly basic was missing: there’s no way to bulk delete posts. No “clear history.” No “delete all.” Just… one-by-one deletion.

I had hundreds of posts.
Manually deleting them was clearly not happening.

The Build (Surprisingly Fast, Thanks to AI)

So I did what most indie hackers would do: I built my own solution.

That’s how DeleteThreads started.

What surprised me most was how fast the actual building part was. With the help of AI and a modern stack (Next.js, Supabase, Cloudflare), the core functionality came together incredibly quickly. AI handled a lot of the repetitive work, which let me focus on logic, edge cases, and the user experience instead of boilerplate.

From a pure coding perspective, this was one of the smoothest builds I’ve done.

The Real Pain: Meta’s API Approval

The real challenge wasn’t technical at all.

It was getting Meta’s API permissions approved.

To make DeleteThreads work properly, I needed threads_delete and threads_read_replies. What followed was weeks of back-and-forth with Meta’s review team — easily 10+ emails explaining use cases, clarifying flows, and responding to rejections and follow-up questions.

In the end, I spent far more time on permissions than on writing code.

Classic modern dev story:

AI helps you ship in days, platform bureaucracy slows you down for weeks.

Launch

Despite all that, DeleteThreads is now live:
👉 https://deletethreads.net

I also recorded a full YouTube demo showing exactly how it works.

I’m sharing this here for anyone else who’s frustrated by their Threads history — and for fellow makers who’ve been through the joys of API approval hell.

Happy to answer any questions about the build, the permissions process, or anything else 🙌