TURN BUGS INTO PROGRESS CAPTURE. UNDERSTAND. PRIORITISE. SHIP.

01 / PRODUCT

The error is a clue.

The replay is the case.

ReplayRequestsConsoleStack

02 / PRODUCT

One failure. One issue.

Every time it hits, it lands on the same ticket.

GroupedWho it hitWhen it last fired

03 / PRODUCT

Before the error,
up to ten minutes.

Recording starts when the browser SDK loads and keeps a rolling buffer. Each report shows the history that was actually captured.

10-min BufferSession TimelineRedacted PII

01 / DEVELOPERS

Your first capture.
Before your next bug.

Create a project key, add the single snippet, then trigger a test error in your app. Open the report and check the evidence.

<script type="module">
  import { init } from
    'https://app.bugtape.ai/bugtape.mjs';

  init({ apiKey: 'YOUR_PROJECT_KEY' });
</script>

Zero dependencies12KB gzipAutomatic reporting

02 / DEVELOPERS

Different apps.
Clear evidence.

Different runtimes provide different evidence. Every report says what was recorded and what was not, so a native or server report is never mistaken for a browser recording.

Web · Full DOM ReplaySwift · Handled & BreadcrumbsServer · Failure context

03 / DEVELOPERS

Bring the issue
to your agent.

After capture, connect an MCP client to inspect the same scoped issue context used in the console. Claude Code, Cursor and Codex are supported MCP clients.

MCP ServerScoped PATsget_repro_context

01 / AGENTS

Give your agent the whole bug.

MCP. No guesswork from a one-line stack.

Claude CodeCursorCodex

MCP is on Pro. Webhooks are on Free.

02 / AGENTS

Capture. Connect.
Investigate.

Point Claude Code, Cursor or Codex at BugTape MCP. The agent reads the issue and occurrence history rather than hallucinating from an isolated error message.

get_repro_contextget_bug_eventslist_bugs

03 / AGENTS

Scoped tokens.
Private by design.

Agents authenticate using workspace-scoped personal access tokens with read-only permissions. Capture keys only ingest; they never expose tokens.

Workspace ScopedAudit TrailZero AI SDK deps

01 / PRICING

Two plans.
One capture flow.

Start free to prove your flow. Upgrade when you need more capacity.

02 / PRICING

Capture first.
Add capacity when it matters.

No credit card required for Free. Product limits apply per plan; the console shows current workspace usage in real time.

No card for FreeUpgrade anytimeTransparent limits

03 / PRICING

Clear answers.

DOM replay runs in a 10-minute rolling buffer before a report. Swift supports handled errors and breadcrumbs. Sensitive data is scrubbed by default.

10-min rolling DOMClient-side scrubbingPrivacy first