


Overview
Record a bug once: replay, console errors and network in one offline file. For QA and devs. Free, no account, no upload.
Record a bug once. Get a report a developer can actually reproduce: a replay of what happened, the console errors, the failed requests and the steps, in one file that opens offline. Free and open source (MIT). No account, no upload, no TraceBug server. ━━━━━━━━━━━━━━━━━━━━ HOW IT WORKS ━━━━━━━━━━━━━━━━━━━━ 1. Click the TraceBug icon → Capture Bug (or press Alt+B). 2. Reproduce the bug. TraceBug records clicks, typing, navigation, console output and network requests. 3. Click Stop. Review the report, then export it or send it to your tracker. Want video too? Turn on "Events + Video". Tab mode records the current tab with no "Choose what to share" dialog (Chrome asks once for permission); Desktop mode records any window or screen. Narrate with your microphone, pick which mic, and blur sensitive areas before you start. ━━━━━━━━━━━━━━━━━━━━ WHAT'S IN A REPORT ━━━━━━━━━━━━━━━━━━━━ • A DOM replay of the session (and the video, if you recorded one) • Console errors and warnings with stack traces • Network requests, with the failed ones flagged • Repro steps: every click, input, select and navigation, in order • Environment: browser, OS, viewport, timezone, connection • Screenshots of the visible area or a cropped region, which you can annotate • A pattern-based hint at the likely cause, e.g. "POST /api/orders failed with 404 after clicking Place order" ━━━━━━━━━━━━━━━━━━━━ FIX IT WITH YOUR AI AGENT ━━━━━━━━━━━━━━━━━━━━ Export the report, then run "npx tracebug mcp". Claude Code, Cursor or any MCP client reads the report locally and works the bug in your codebase. It can also generate a failing Playwright test from the repro steps. Nothing is uploaded. ━━━━━━━━━━━━━━━━━━━━ EXPORT AND SHARE ━━━━━━━━━━━━━━━━━━━━ • One self-contained .html replay anyone on your team can open offline • GitHub, Linear and Slack, with your own token (TraceBug asks before each send) • Jira markup, Markdown, .zip, HAR, and a failing Playwright test (.spec.ts) ━━━━━━━━━━━━━━━━━━━━ PRIVATE BY DEFAULT ━━━━━━━━━━━━━━━━━━━━ • Reports and settings stay on your device. Nothing is sent to TraceBug. • No access to any site until you click Capture on it, and never to all sites at install. • Passwords, tokens, card numbers and secret URL parameters are masked as they're captured. Add your own redaction rules for anything else. • Blur any element before or during a recording. • No analytics, no telemetry, no remote code. • Site access is asked for only when you capture, never for all sites at install. • Open source: github.com/prashantsinghmangat/tracebug-ai ━━━━━━━━━━━━━━━━━━━━ WHO IT'S FOR ━━━━━━━━━━━━━━━━━━━━ QA engineers, frontend developers, and anyone who has had to answer "can you send me the steps?" ━━━━━━━━━━━━━━━━━━━━ LINKS ━━━━━━━━━━━━━━━━━━━━ • Website and live demo: https://tracebug.dev • Source: https://github.com/prashantsinghmangat/tracebug-ai • npm SDK (add TraceBug to your own app): https://www.npmjs.com/package/tracebug-sdk • Issues and feedback: https://github.com/prashantsinghmangat/tracebug-ai/issues
5 out of 53 ratings
Details
- Version1.11.4
- UpdatedOctober 31, 2026
- Size628KiB
- LanguagesEnglish
- DeveloperWebsite
Email
prashantsinghmangat5@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
TraceBug: Bug Report Recorder & Replay has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
TraceBug: Bug Report Recorder & Replay handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site