TraceBug icon

TraceBug

TraceBug is a browser-based bug reporting tool that captures a failing session and exports it as a self-contained HTML report for local review.

TraceBug

What TraceBug is

TraceBug is a browser-based bug reporting tool that captures a failing session and packages it into a single HTML file a developer can open locally. The export includes replay, console errors, network requests, screenshots, and a root-cause hint so the report carries more than a static screenshot or a vague ticket description.

The product is built around a local-first workflow: anyone can capture and export a report without creating an account, uploading data, or setting up a backend. For hand-off, the exported file can be shared directly or read by an AI coding agent through TraceBug’s local MCP server, which is designed to work with tools such as Claude Code, Cursor, Windsurf, and VS Code.

Core capabilities

One-step bug capture

Capture a bug in one browser shortcut or a quick export flow. TraceBug records the session automatically so the report includes what happened without a manual write-up.

Offline HTML reports

Bundle the full session into a single .html file that can be opened offline. The exported report is self-contained, so it can be sent as a file instead of requiring a login or hosted link.

Session evidence in one report

Include the evidence a developer usually needs to reproduce a failure: replay, console errors, network calls, screenshots, and a timeline of user actions.

Root-cause hints

Surface a root-cause hint at the top of the report. The site shows the suspected failing request or exception before the rest of the session details, helping a developer start in the right place.

Developer hand-off tools

Export reports to GitHub, Linear, Slack, and PDF, with Chrome extension and npm SDK options listed on the pricing page. The docs also describe a local MCP server for AI agents.

Collaboration and deployment options

Support local and team workflows with options for cloud sharing, workspace roles, activity feeds, quotas, analytics, Google SSO, and self-hosting in higher tiers.

Where TraceBug fits

  • Capture a reproducible bug report quickly

    A tester or support person hits a bug in a browser app and needs to preserve the exact sequence of clicks, requests, and errors without filling out a long form.

  • Debug a report without a hosted portal

    A developer receives a file from Slack, email, or a ticket attachment and wants to inspect the console trace, network failures, and timeline offline before opening the codebase.

  • Let an AI agent triage the bug

    A team wants to hand bug reports to Claude Code, Cursor, or another MCP client so an AI agent can read the export and investigate the likely root cause.

  • Coordinate bug handling across a team

    A small team wants shared workspaces, auto-sync to issue trackers, and role-based collaboration instead of only local files.

  • Use a self-hosted deployment

    An organization needs self-hosting, SSO, audit logs, and custom retention controls for a more governed deployment.

Pros and Cons

Pros

  • Captures the bug as a self-contained HTML report that can be opened offline.
  • Includes multiple evidence types in one file, which reduces back-and-forth about what happened.
  • Works without an account or server for the core local capture flow.
  • Provides a local MCP server for AI coding agents to inspect bug reports directly from disk.
  • Offers clear paths for solo use, team sharing, and self-hosted deployment.

Cons

  • Several collaboration, AI, and enterprise capabilities are marked as coming soon or are only available in paid tiers.
  • The published workflow is centered on browser capture and local file export; the site does not show a native mobile or desktop capture app.
  • Team and enterprise capabilities add more setup and policy control, but the source does not show full implementation details for every integration or workflow.

FAQ

What does TraceBug export?

TraceBug is designed to capture a bug as a self-contained HTML file with session replay, console errors, network requests, screenshots, and a root-cause hint. The report can be opened offline by a developer or handed to an AI coding agent through the MCP server.

Is TraceBug free to use?

The home page says the core capture flow is free, with no account and no server required. The pricing page adds that local bug capture and offline HTML exports are free forever, while collaboration features are paid when teams want cloud sharing, integrations, or self-hosting.

Can TraceBug connect to AI coding agents?

The docs describe a local Model Context Protocol server that reads exported HTML reports from disk and works with Claude Code, Cursor, Windsurf, VS Code, and any MCP client.

What platform does TraceBug run on?

The source does not describe a mobile app or desktop app. The published workflow is browser-based: capture in the browser, export an HTML file, then share or open it locally.

Does TraceBug have team and enterprise plans?

The pricing page shows three paid tiers in addition to the free local capture workflow: Pro for individual cloud sharing, Team for shared workspaces and auto-sync, and Enterprise for self-hosted deployment and compliance-oriented controls. Several paid features are marked as coming soon.

Quick Facts

Category
Developer Tool
Primary workflow
Browser capture → offline .html export → local handoff or AI debugging
Platform
Web / browser-based
Source domain
tracebug.dev
License
MIT licensed / free and open source
Pricing shape
Free local capture, with paid collaboration and self-hosted tiers