Developer Guide

TraceGist helps you catch and fix bugs in any application that runs in the browser. Spend less time chasing context and more time shipping — the extension captures everything your agent needs to reproduce and fix an issue.

How it fits into your workflow

  1. Install the extension on your own machine to record sessions while you develop and test locally. Use it the same way a tester would — start a recording, reproduce the issue, export the session.

  2. Share the extension with your testers. Send them the install link. They record their sessions and hand you back the exported ZIP. No accounts, no uploads — everything stays local.

  3. Set up the MCP bridge so your coding agent can read session packages directly. Once configured, you can hand a session to your agent and let it diagnose the bug, read the interaction timeline, inspect network failures, and generate a Playwright repro script — without you having to describe anything.

Setting up the MCP bridge

Follow the agent integration guide to connect the bridge to Claude Code, Cursor, or any other MCP-compatible agent.

Once connected, ask your agent something like:

Read the latest TraceGist session and tell me what went wrong.

The agent will read the session package, including interaction logs, JS errors, failed network requests, environment snapshots, and any voice markers the tester left.

Typical bug fix flow

  1. Tester records a session and exports the Agent Session Export ZIP.
  2. They send you the ZIP file (or drop it in your Downloads folder).
  3. You ask your coding agent to read the session and propose a fix.
  4. The agent uses the MCP tools to inspect the session and can run the generated Playwright repro script to confirm the fix.