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).
TraceBug
Instant bug reports your AI agent can actually debug
Capture a browser bug in two clicks: session replay, console errors, network requests, screenshots, and a repro timeline in ONE offlinehtml file. A local MCP server lets Claude Code, Cursor, or Windsurf debug from real evidence. Free, MIT, no account.
Hey Product Hunt! 👋
I built TraceBug because I was living both halves of a bad loop: receiving bug reports that said "checkout is broken" with a cropped screenshot, and then pasting console output into Claude by hand to debug my own bugs.
TraceBug fixes both halves:
🐛 Capture — a free Chrome extension (or npm SDK) records what actually happened: session replay, console errors with stack traces, network requests, screenshots, and a millisecond repro timeline. Two clicks, one self-contained .html file that opens offline. No account, no server, nothing uploaded — there is literally no backend.
🤖 Hand it to your AI — npx -y tracebug mcp starts a local MCP server (stdio-only, zero network connections) so Claude Code, Cursor, or Windsurf can read the evidence directly. We published an unedited transcript of Claude going from crash to root cause in five tool calls: tracebug.dev/proof — I'd rather show you than tell you.
Honest limitations, so you don't find them the hard way:
The extension is Chrome-only today (npm SDK works in any app)
Replay is rrweb-based, so canvas/WebGL-heavy apps lose visual fidelity
TraceBug ships evidence, not an LLM — the AI investigation uses your own agent
It's MIT-licensed and free — the whole pipeline runs on your machine, which I think is the one thing cloud bug-reporting tools structurally can't copy.
Try it in 30 seconds without installing anything: tracebug.dev/try.html has intentional bugs waiting to be captured.
I'll be here all day — tell me what's missing, and I mean it. The roadmap after today is literally built from what early users say.
the offline html file idea is genuinely clever, been waiting for something like this. one thing though, would be really helpful if the repro timeline could auto detect sensitive stuff like api keys or auth tokens and mask them before saving, otherwise it's risky to share those files with teammates
One thing that would make this a no-brainer for me: support attaching the offline html repro directly to GitHub issues via a simple drag and drop helper or a small CLI flag that creates the issue with the file uploaded. Right now the workflow ends at "here's the file" but most bug reports live in issues, so closing that loop would really seal the deal.
single offline html file with everything bundled is genuinely clever, way easier to share repros than hopping between loom and slack
Honestly, the offline HTML export is a killer feature. One thing that would make it even better is if the repro timeline could include console.warn and console.info logs by default, not just errors. I often miss those when debugging state transitions.
the offline single html file approach is genuinely clever, it sidesteps all the usual sharing headaches and keeps everything self contained. love that you wired it straight into claude code through a local mcp instead of forcing yet another web app.
A small thing that would make this way more useful for my team: add a way to redact sensitive fields before sharing the html file. Sometimes the bug repro includes customer tokens or PII in network payloads, and I can't send the file as-is to our support channel.
Offline html file with everything bundled is such a clever move, no cloud upload needed and I can just attach it to a ticket or paste it into a prompt. The MCP integration with Cursor feels like the right way to actually act on a bug instead of just staring at logs.
Saved a tricky repro as a single html file and opened it offline later, everything still worked. The local MCP hookup with Claude Code actually pulled useful stuff from the timeline instead of guessing.
Works exactly as advertised, captured a tricky CSS bug in under a minute and the offline html file is genius for sharing without granting access to internal tools.
About TraceBug on Product Hunt
“Instant bug reports your AI agent can actually debug”
TraceBug was submitted on Product Hunt and earned 23 upvotes and 21 comments, placing #31 on the daily leaderboard. Capture a browser bug in two clicks: session replay, console errors, network requests, screenshots, and a repro timeline in ONE offlinehtml file. A local MCP server lets Claude Code, Cursor, or Windsurf debug from real evidence. Free, MIT, no account.
TraceBug was featured in Chrome Extensions (52.7k followers), Developer Tools (516.2k followers), Artificial Intelligence (474.1k followers) and GitHub (41.3k followers) on Product Hunt. Together, these topics include over 224.1k products, making this a competitive space to launch in.
Who hunted TraceBug?
TraceBug was hunted by Prashant Singh. 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 TraceBug stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Prashant Singh