TraceBug icon

TraceBug

Revendiquer

TraceBug is a local-first bug reporting tool that turns browser issues into a self-contained .html report for offline developer hand-off, with local MCP debugging and export options.

TraceBug

Overview

TraceBug is a local-first bug reporting tool that packages a user’s session into a single .html report. The report can include replay, console errors, network requests, screenshots, and captured steps so a developer can open it offline and see what happened.

The product is aimed at the hand-off from tester to developer. Instead of asking someone to retype reproduction steps or paste screenshots into a form, TraceBug turns the bug into a file that can be sent directly, exported into ticket formats, or read by an AI coding agent through its local MCP server.

Features

Offline HTML bug reports

Records the user journey into one self-contained .html file so the report can be opened offline and shared like a normal file, not a hosted ticket.

Multi-signal capture

Captures the session replay together with console errors, network requests, screenshots, and the user actions that led to the bug.

Root-cause hints

Adds a root-cause hint at the top of the report, helping the developer see the likely failing request or exception before scrolling through the trace.

Multiple export formats

Provides export paths for GitHub issue, Jira ticket, PDF, and JSON, so the same capture can be adapted to different hand-off workflows.

Local MCP agent support

Ships with a local MCP server that lets Claude Code, Cursor, Windsurf, VS Code, or another MCP client read reports from disk and investigate them.

Browser and SDK capture

Offers a Chrome extension and npm SDK for capture, with offline local bug handling available before any paid collaboration features.

Use Cases

  • Hand off a browser bug quickly

    A tester hits a bug in the browser, captures it with one shortcut, and sends the exported file to a developer without filling out a long form.

  • Debug from a self-contained report

    A developer opens the exported .html report offline to inspect the replay, console error, failed request, and screenshots before starting a fix.

  • Let an AI agent inspect the report

    An engineering team uses the local MCP server so Claude Code, Cursor, Windsurf, or VS Code can read a report from disk and investigate the likely cause.

  • Route reports into existing workflows

    A team that prefers issue trackers exports the same capture into GitHub issue, Jira ticket, PDF, or JSON formats instead of keeping it as a browser file.

  • Start with local capture and expand later

    A product or support team captures a recurring bug locally first, then decides later whether to use cloud sharing or future team plans for collaboration.

Pros and Cons

Pros

  • Captures a bug into one offline file that a developer can open immediately.
  • Includes several kinds of evidence in the same report: replay, console output, network activity, screenshots, and steps.
  • Works without an account or upload flow for the core capture and share experience.
  • Supports developer hand-off through GitHub, Jira, PDF, JSON, Slack, and Linear-oriented workflows.
  • Offers a local MCP server for AI-assisted debugging directly from the exported report.

Cons

  • Paid collaboration plans are marked coming soon, so the current public offering is centered on local capture rather than full cloud team workflows.
  • The stronger AI-agent workflow depends on using the MCP server and a compatible client, which adds an extra setup step for teams that want that path.

FAQ

What does TraceBug export?

TraceBug captures a bug as a self-contained .html report. The report includes session replay, console errors, network activity, screenshots, and root-cause hints, so the developer can open it offline without needing an account or upload flow.

Is TraceBug free to use?

The browser extension and local capture flow are presented as free. The pricing page says local bug capture and offline .html exports are free forever, while paid plans are reserved for collaboration features such as shareable URLs, integrations, and self-hosting when those are needed.

How does TraceBug work with AI coding agents?

TraceBug’s MCP server runs locally over stdio. The docs say you can point an MCP client such as Claude Code, Cursor, Windsurf, or VS Code at a folder of exported reports so an agent can read the report from disk and debug against your codebase.

What ways can a report be shared?

The source pages show exports for GitHub issues, Jira tickets, PDF, and JSON, plus Slack and Linear mentioned in the pricing page. The MCP docs also describe a local hand-off workflow for sending the exported .html file to a developer or agent.

Does TraceBug offer team or enterprise features?

The site describes a free local-first product, plus coming-soon paid plans for Pro, Team, and Enterprise. Pro adds cloud sharing and branding features, Team adds shared workspaces and auto-sync, and Enterprise adds self-hosting and compliance-oriented controls.

Quick Facts

Category
Developer Tool
Product type
Local-first bug reporting and hand-off tool
Primary output
Self-contained .html bug report
Capture methods
Chrome extension and npm SDK
AI workflow
Local MCP server for agent debugging
Pricing shape
Free local capture; paid collaboration plans are coming soon

Analyses de TraceBug

Les données de trafic sont fournies à titre indicatif uniquement.

Trafic et classements

Visites mensuelles
0
Durée moyenne de visite
00:00
Pages par visite
0.00

Tendances du trafic

Principales régions

Les analyses de trafic ne sont pas encore disponibles.

Sources de trafic

  • Direct: 0.00%
  • Recherche: 0.00%
  • Référents: 0.00%
  • Réseaux sociaux: 0.00%
  • E-mail: 0.00%
  • Publicités display: 0.00%