DebugBundle Documentation

Understand incidents, bundles, local-first capture, and agent-readable output.

Capture an error locally, process it, and inspect the resulting bundle.

Choose the CLI, SDK, browser relay, or self-host path for your stack.

Node.js, Browser, Python, PHP, Java, .NET, Go, Ruby, Android, iOS, React Native, and WordPress capture options with the same DebugBundle event model.

Add backend PHP capture, frontend browser capture, and a token-safe same-origin relay to WordPress.

Setup, local processing, inspection, log ingestion, cloud connection, and automation output.

Ingestion, retrieval, webhooks, alerts, availability checks, projects, probes, members, and billing endpoints.

Failure bundles, improvement bundles, grouping, reproduction artifacts, and schema details.

Send signed lifecycle events and alert teams through email, Slack, Discord, or webhooks.

Give AI coding agents tool access to incidents, bundles, health checks, probes, alerts, and project operations.

Redaction, token scope separation, webhook signatures, retention, and privacy controls.

Run hosted health checks against public endpoints and open normal DebugBundle incidents when they fail.

Request additional diagnostic data from SDKs without code changes or redeployment.

Control which events become incidents, which remain context, and how repeated operational noise is handled.

Use MCP, CLI output, and bundle artifacts from agent-capable development environments.

Connect repository dispatch, reference fetching, and repository-owned GitHub Actions.

Review the complete tool surface that agents can call from MCP-compatible environments.

Start from the generated reference overview.

Generated from the public OpenAPI document.

Generated from the shipped CLI usage surface.

Generated from the implemented MCP tool catalog.

Generated from the webhook event contract.

Generated bundle schema and example artifacts.

Generated profile schema and project configuration artifacts.

Generated API, CLI, and validation error catalog.