About
Production evidence for your coding agent.
DebugBundle brings the captured evidence for a production incident into one structured artifact: the debug bundle.
A coding agent can inspect your repository. To investigate a production failure, it also needs evidence from the running application: the error, the request, related logs, and the release involved.
DebugBundle captures and groups failures, assembles the available evidence into versioned JSON, and exposes bundles through API, CLI, MCP, and the dashboard. Request replay artifacts are generated when captured context supports them. Developers and agents can inspect the evidence, gather missing context, and test a proposed fix.
The project is built with a local-first architecture. You can capture, process, and inspect incidents without DebugBundle Cloud anywhere you control the filesystem and can run the CLI, from a laptop to a self-managed server. The hosted platform adds team collaboration, longer retention, remote probes, and automated improvement analysis, but the core debugging workflow is not locked behind the hosted service.