BugTape groups failures into issues with DOM replay, network, and console evidence — then hands the pack to Claude Code or Cursor over MCP. Humans approve the PR; agents do the reading.
import { init } from '@bugtape/sdk' · Pro unlocks MCP · Free: 100 issues / monthRepeated bugs roll up into one grouped issue, but every occurrence keeps its own user, session, release, environment, and timestamp. The first screen answers who was affected, when it last happened, whether it is spreading, and which replay to open first.
Like a DVR, BugTape silently keeps the last 10 minutes of DOM changes, network requests, console logs, and errors in a bounded in-memory buffer. When a bug is reported, the report arrives with the session, URL, environment, and device context you actually need — nothing is shipped until then.
BugTape generates titles, severity, likely repro steps, and suggested investigation paths from the captured session data — the replay, the console, the network trail. Use AI where it helps, not as the whole story: every claim links back to the event that supports it.
The token refresh fires twice when two tabs share a session. The second refresh rotates the token the first request already holds, so POST /api/payments/intent is sent with a revoked bearer and the summary renders before the retry resolves.
BugTape is strongest when you need the grouped issue and the specific affected session at the same time.
Watch exactly what the user saw and did. Full DOM replay with mouse movements, clicks, scrolls, and page transitions.
Capture pixel-perfect screenshots and draw on them to highlight exactly where the bug is. Colors, arrows, text — all built in.
Users can record a voice description of the bug. Automatically transcribed by Whisper and included in the report. No typing needed.
Manifest V3 extension with side panel and early error buffering. Works on any site without code changes — catches CSP violations, resource loading errors, and page-load errors other tools miss.
Continuous browser capture with bounded buffers and replay sampling — the data needed to turn one report into a grouped issue with real affected-user context.
Watch new occurrences arrive in real time, then jump straight into the affected issue with the specific session and user context that triggered it.
A browser starts recording. A real person hits the bug. One grouped issue appears with the exact user, session, and occurrence you need to inspect next.
Two lines of JS or the Chrome extension. BugTape starts recording DOM mutations, network activity, console output, and errors inside a 10-minute ring buffer. Nothing is shipped until a bug is reported.
DOM · network · console · errorsThe user or tester clicks the bug button and describes what went wrong. The report arrives with the screenshot, note, session, URL, environment, and device context you actually need.
screenshot · voice note · environmentRepeated failures become one grouped issue while every occurrence stays underneath it — how many users hit it, when it started, and which sessions are affected.
grouped issue · affected users · releaseOpen the grouped issue, jump into the exact occurrence, and inspect the events, environment, screenshot, and user trail without guessing which report mattered most.
issue detail · timeline · replayInstall the SDK, initialise it with your project key, and BugTape starts recording. That's the whole integration.
npm install @bugtape/sdk
import { init } from '@bugtape/sdk'; init({ apiKey: 'bt_your_key' }); // recording starts — widget appears bottom-right
Both options land in the same BugTape console. The difference is whether the capture entry point lives inside your product or inside your team's browser.
Mixpanel, Datadog, Sentry, BugTape, and DevTools each own a different part of the debugging lifecycle. They're complementary — here's where each one shines.
"Conversion dropped 5% this week"
"P99 latency spiked, API errors up 3x"
"TypeError in checkout.js, 47 times today"
"Here's exactly what the user did, with AI analysis"
"Set breakpoint, inspect state, profile memory"
We use DevTools every day. It's the best local microscope shipping — the Recorder panel, Performance tab, Issues pane, and Gemini's "explain this error" are remarkable.
DevTools has one blind spot: it only runs when a developer is sitting at the keyboard. It captures nothing from the user on a 4G connection in Karachi who hits a checkout bug at 2 AM on mobile Safari.
BugTape captures that session — the last ten minutes of DOM, network, and console — scrubs PII, fingerprints the error, dedupes it against the 43 other users who hit the same thing, and drops it in your inbox with an AI summary and a ticket link.
DevTools is the developer's microscope on localhost. BugTape is the user's black box recorder on production.
Complementary tools solve different problems — use them alongside BugTape. Alternatives overlap with BugTape's problem space.
| Complementary | Alternatives | |||||
|---|---|---|---|---|---|---|
| Feature | BugTape | Sentry | Datadog | Mixpanel | LogRocket | Jam.dev |
| User-initiated bug reports | ✓ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Automatic error detection | ✓ | ✓ | ✓ | ✗ | ✓ | ✗ |
| Always-on session recording | ✓ Ring buffer | ● Breadcrumbs | ✗ | ✗ | ✓ Full DOM | ✗ |
| Multi-provider AI triage | ✓ 5 providers | ✗ | ✗ | ✗ | ✗ | ● GPT only |
| Chrome extension | ✓ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Embeddable SDK | ✓ Browser SDK | ✓ ~72kB | ✓ Agent | ✓ ~40kB | ✓ ~200kB | ✗ |
| Screenshot annotation | ✓ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Voice notes | ✓ | ✗ | ✗ | ✗ | ✗ | ✗ |
| APM & distributed tracing | ✗ | ● Basic | ✓ | ✗ | ✗ | ✗ |
| Infrastructure monitoring | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| Log aggregation | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| Conversion funnels | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ |
| Retention & cohort analysis | ✗ | ✗ | ✗ | ✓ | ✗ | ✗ |
| Works without event instrumentation | ✓ Automatic | ✓ Errors only | ✗ Agent setup | ✗ Manual setup | ✓ | ✓ |
| Debug individual user sessions | ✓ Full replay | ● Breadcrumbs | ✗ Traces only | ✗ Aggregate only | ✓ | ✗ |
| Network request capture | ✓ Full detail | ● Minimal | ✓ Backend | ✗ | ✓ | ✗ |
| Console log capture | ✓ | ● Breadcrumbs | ✓ Server logs | ✗ | ✓ | ✗ |
| Non-engineer friendly | ✓ | ✗ | ✗ | ✓ | ✗ | ✓ |
| E2E encryption | ✓ AES-256-GCM | ✗ | ✗ | ✗ | ✗ | ✗ |
| PII auto-scrubbing | ✓ | ✓ Basic | ✓ Basic | ✗ | ✓ Basic | ✗ |
| Open source | ● SDK (Apache-2.0) | ✓ | ✗ | ✗ | ✗ | ✗ |
| Free tier | ✓ 100 bugs/mo | ✓ 5K errors/mo | ✓ 14-day trial | ✓ 20M events/mo | ✓ 1K sessions/mo | ✓ Limited |
BugTape fires webhooks instantly when bugs arrive — right to the tools your team already lives in.
BugTape implements defense-in-depth security at every layer. Sensitive data is scrubbed before it ever enters memory, reports are encrypted client-side, and only you hold the keys.
Emails, credit cards (Luhn-validated), SSNs, phone numbers, JWTs, API keys, and bearer tokens are detected and masked at capture time — before data enters the ring buffer. Sensitive data never touches memory in cleartext.
Layer 1: captureBug reports are encrypted client-side using AES-256-GCM. Each report gets a unique 96-bit IV and 128-bit salt. Keys are derived using PBKDF2-SHA256 with 100,000 iterations.
Layer 2: transitBugTape servers never see your encryption key. Reports are encrypted before leaving the browser. Only your team can decrypt them — we literally cannot read your data, even if subpoenaed.
Layer 3: storageThe ring buffer auto-deletes events older than 10 minutes. No long-term storage of user sessions. If no bug is reported, the data simply vanishes. Memory-only — nothing written to disk.
Data minimizationDefine custom PII patterns, choose which fields to always redact, and whitelist safe fields. Default redact list includes password, token, apikey, authorization, credit_card, ssn, cvv, and more.
CustomizableNo tracking. No third-party data sharing. Data processing happens entirely in the browser. Self-host option means your data never leaves your infrastructure.
ComplianceProduction API deployments can enforce explicit CORS allow-lists with exact origins, wildcard subdomains, and extension-origin patterns. Lock traffic to only the domains you trust.
PerimeterIngest endpoints require project-scoped API keys, then enforce per-key throttling and backend validation. Invalid or rotated keys are rejected before write operations.
Abuse protectionBugTape.init({
apiKey: 'bt_...',
// AES-256-GCM encryption (reports encrypted before leaving browser)
encryptionKey: 'your-secret-key',
// PII scrubbing (on by default, customize patterns)
pii: { redactFields: ['password', 'ssn', 'custom_field'] },
// Secure endpoint
endpoint: 'https://api.your-domain.com/v1/ingest',
// Backend CORS allow-list example: https://console.your-domain.com,chrome-extension://*
})
Free for the console. Pro unlocks the agent loop — the reason to pay.
Self-serve only. No sales call. Enterprise SSO/SOC2 is not year-1 — talk to us if you need it later. Annual = 2 months free on Pro/Team.
Install the SDK, open the console, connect MCP on Pro — your next production bug can become a PR.