Replay the page
Up to ten minutes of bounded DOM activity, subject to session age and event limits. DOM reconstruction, not screen video.
Product
The same bug lands twice. Fix that first.
Matching failures stay under one issue. Each occurrence keeps its time and platform. Browser evidence stays with the occurrence that captured it.
Demo: no account; report stays in the tab. Setup: one project key and one test error.
Same bug twice
Work the problem, not the copies.
Matching reports attach to one issue. Each occurrence keeps its time, platform, release, environment and available identity.
Evidence without pretending.
Evidence varies by runtime and capture settings. The issue detail shows what exists and labels what does not.
Follow the failure
Request metadata, console output, errors and stack frames can stay with the browser occurrence.
See who hit it
Identified users appear when the client supplied identity. Anonymous reports remain anonymous.
One user, or everyone?
Inspect the slice, then check the roster.
Move between occurrences without losing the issue. Replay, network, console and stack stay scoped. Identified users show who hit it.
Web installation
One key. One module. One test error.
Create a free project, copy its project key from Setup, then add the hosted browser module. The npm package is not public.
- Create a project
Setup mints a
bt_live_*project key and shows it once. - Paste the module
Initialize once after your app's consent policy allows capture.
- Trigger a named test error
Wait for the ingest acknowledgement, then open that exact occurrence.
Browser · hosted ES module
<script type="module">
import { init } from 'https://app.bugtape.ai/bugtape.mjs';
init({ apiKey: 'bt_live_your_key_here' });
</script>Different runtimes. Clear limits.
All supported reports reach the same inbox, but they do not contain the same evidence.
DOM, request, console and error context
Replay depends on captured DOM events. Configure privacy and scrubbing for your app.
Handled errors and breadcrumbs
No browser replay. Fatal native crash capture and symbolication are not claimed.
The context your sender provides
Server reports do not create browser history. Send platform, stack and relevant metadata explicitly.