Launched this week
TraceBug
Instant bug reports your AI agent can actually debug
24 followers
Instant bug reports your AI agent can actually debug
24 followers
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.
single offline html file with everything bundled is genuinely clever, way easier to share repros than hopping between loom and slack
@idemod4m Thank you! The Loom + Slack + "wait, which thread was the console screenshot in?" shuffle is exactly the tax this removes one file, everything in it, works offline. If anything's still missing from the bundle when you share a repro, tell me the roadmap this week is literally being built from these comments.
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.
@kazmmersinqkcj This is the exact loop I built it for file survives offline, agent reads evidence instead of guessing. "Pulled useful stuff from the timeline instead of guessing" is going on a sticky note above my desk. If you hit a session where Claude does end up guessing, send me that file those are the ones that improve the timeline format.
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.
@kriyexqxx Thanks! "Attach it to a ticket or paste it into a prompt" you've described the two halves of the design in one sentence: the same file works for a human reviewer and an AI agent, no translation step. Curious how the Cursor MCP flow holds up on your real bugs that path is newer than the Claude Code one, so honest reports welcome.