This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
agent-leftovers
Find the cloud bills your AI coding agent left running
Claude Code and Codex create VMs, databases and deploys mid-task, then forget them. agent-leftovers reads the logs they already keep on your machine and lists every leftover with the exact command to turn it off. Read-only, local, free.
I kept reading the same story: someone lets Claude Code or Codex finish a task, and a week later finds a GPU VM, a 250 GB disk or a batch script hammering a paid API with their key. The agent made it; nobody remembered it.
Your agent already writes down every command it runs in local session logs. agent-leftovers reads them and answers one question: what did my agent create that is still out there, and how do I turn it off?
• 59 rules across GCP, AWS, Azure, Cloudflare, Vercel, Fly, Supabase, Heroku, Terraform and more
• Skips what the agent already deleted and creates that failed
• Flags scripts the agent wrote that call OpenAI, Anthropic or Gemini with your key, even ones left running in the background
• Read-only and fully local: it runs nothing and sends nothing
Try it: npx github:ApahSaroj/agent-leftovers
Honest limit: it only sees the agent's shell. Things made through MCP tools or a web console won't show.
What should I add next: live "is it still running?" checks, or support for Cursor and Gemini CLI?
The smart move here is reading the agent's own session logs instead of asking for cloud credentials — no new access handed over, it just audits what Claude Code and Codex already wrote down. Honestly the flag I like most is the one for orphaned scripts still calling the model APIs with your own key: a forgotten VM bills you quietly, a forgotten script can bill you creatively. And shipping the MCP coverage plus --verify in v0.2 was the right call — a leftover list that's a week stale is worse than none.
Update: v0.2 is out, built from today's feedback.
• It now catches resources your agent created through MCP servers (Supabase, Neon, Vercel, Cloudflare, DigitalOcean, E2B and more), not just shell commands.
• New optional --verify flag asks your own cloud CLIs which leftovers still exist. Read-only describe/list calls only, off by default.
Still free, zero dependencies, and nothing leaves your machine unless you pass --verify.
npx github:ApahSaroj/agent-leftovers
Thanks to everyone who pointed out the MCP blind spot. Keep it coming.
About agent-leftovers on Product Hunt
“Find the cloud bills your AI coding agent left running”
agent-leftovers was submitted on Product Hunt and earned 2 upvotes and 4 comments, placing #103 on the daily leaderboard. Claude Code and Codex create VMs, databases and deploys mid-task, then forget them. agent-leftovers reads the logs they already keep on your machine and lists every leftover with the exact command to turn it off. Read-only, local, free.
agent-leftovers was featured in Open Source (69.1k followers), Developer Tools (523.3k followers), Artificial Intelligence (484k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 287.2k products, making this a competitive space to launch in.
Who hunted agent-leftovers?
agent-leftovers was hunted by Saroj Kumar Nayak. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how agent-leftovers stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hi Product Hunt!
I kept reading the same story: someone lets Claude Code or Codex finish a task, and a week later finds a GPU VM, a 250 GB disk or a batch script hammering a paid API with their key. The agent made it; nobody remembered it.
Your agent already writes down every command it runs in local session logs. agent-leftovers reads them and answers one question: what did my agent create that is still out there, and how do I turn it off?
• 59 rules across GCP, AWS, Azure, Cloudflare, Vercel, Fly, Supabase, Heroku, Terraform and more
• Skips what the agent already deleted and creates that failed
• Flags scripts the agent wrote that call OpenAI, Anthropic or Gemini with your key, even ones left running in the background
• Read-only and fully local: it runs nothing and sends nothing
Try it: npx github:ApahSaroj/agent-leftovers
Honest limit: it only sees the agent's shell. Things made through MCP tools or a web console won't show.
What should I add next: live "is it still running?" checks, or support for Cursor and Gemini CLI?