Use BugCapsule
Dashboard
Find a captured failure, read what was recorded around it, copy the replay and verify commands, review verification results, share a capsule, and manage capture settings. Replays themselves run on your machine through the CLI; the dashboard shows the commands and the results the CLI records.
Sign in with the account your BugCapsule team gives you. Sessions last 12 hours.
Overview
The project home shows counts for New, Reproduced, Fixed and Eligible for replay, capsules by status, the most recent capsules, and the latest replay and verification results. For very large projects the counts show a minimum ("1,000+") rather than an exact total.
Capsules
The list is newest first. Filter by status, capture mode, app version, eligibility, failure signature or platform, and page through with Next.
| Status | Means |
|---|---|
new | Uploaded, not replayed yet |
reproduced | A bugcapsule run reproduced it |
not_reproduced | Every requested replay attempt ran cleanly without the failure |
fixed | A bugcapsule verify was clean in every requested attempt after it had been reproduced |
ineligible | Can't be replayed (usually a manual capture with no failure assertion) |
archived | Set by you when triaging |
The capsule workspace
| Tab | What's there |
|---|---|
| Summary | The failure (type, message, signature), replay eligibility and what's missing, the latest results, and triage: status, issue link and notes |
| Timeline | Every recorded event in time order, with an inspector for the selected event |
| Events | The raw event list: touches, actions, text, lifecycle, routes, logs |
| Network | Each HTTP exchange: method, URL, status, latency, headers and bodies (as redacted on the device) |
| State | The checkpoint replay starts from: allowlisted storage, route, registered state |
| Environment | App version and build, git commit, platform, OS, screen, SDK, capabilities |
| Runs | Every replay and verify result recorded by the CLI, with attempts and the commit tested |
The commands drawer gives you ready-to-paste CLI lines for this capsule: bugcapsule inspect, run -n 3, verify -n 5, regress add … --name, regress run, and the bugcapsule login line for your project.
Share, archive, delete
- Share creates a public download link that expires (72 hours by default, up to 30 days). Anyone with the link can download the capsule until it expires or you revoke it; revoking removes every active link for that capsule.
- Archive sets the status to
archived. - Delete removes the capsule, its run history and its share links right away. It can't be undone.
Capture settings
These apply to every device running your app, at its next settings refresh (5 minutes by default, and whenever the app returns to the foreground).
| Setting | Effect |
|---|---|
| Capture enabled | The kill switch. Off: uploads are refused at once; devices stop recording and delete queued captures. Same as bugcapsule capture --on. |
| Production sample rate | Share of production sessions that record. It can only lower the cap built into your app (default 10%). |
| Maximum capsule size | Larger uploads are refused (default 5 MB) |
| Network body capture | Off: request and response bodies stop being recorded, including ones already buffered on devices |
| Extra redaction keys | Field names redacted on every device, on top of the built-in rules and your app's own |
| Config refresh interval | How often devices re-check these settings |
SDK setup
A checklist for wiring the SDK into an app. It ticks itself off when your project receives its first capsule and its first replay result.
Project settings and keys
Shows the project and lets you rotate keys.
Rotating the ingest key stops every app build already shipped from uploading, immediately and with no overlap, until a build with the new key ships. Rotate it only if it must be revoked. Rotating the secret key affects only the CLI, CI and dashboard; the new key is shown once, so update bugcapsule login and your CI secrets straight away.