Capture

Capture the console log, not a description of it

When a bug is reported — through the widget, the app or email — the evidence travels with it: the console log that was firing, a screenshot of the broken state, a recording of how the reporter got there.

new report · ACME-483rec
console
ScreenshotRecording 00:12Safari 26 · iOS · 390×844

The evidence set

Console log capture

The errors that were firing, recorded at report time — the difference between "cannot reproduce" and a five-minute fix.

Screenshots

Pixel evidence of the broken state, attached to the ticket.

Screen recordings

Up to 50MB per report — stored and attached automatically.

Environment metadata

Browser, OS, viewport and URL — no interrogating the reporter.

50MB
per recording
30
free captures / month
on paid plans
90d
audit trail
One record of truth

Evidence stays with the ticket

No link-outs to a separate replay tool — attachments live next to the discussion, the sprint assignment and the linked pull request. AI drafting and MCP agents read the same context.

Capture-first competitors stop at collection: Bird Eats Bug Usersnap Userback Gleap
STO-495 MEDIUM BUG

Search input resets while typing

screenshot.png

console

✕ TypeError: value is null

⚠ retry fired ×3

last 200 lines attached

recording · 0:42
LF MD
Ready to triage

From capture to shipped fix

  1. Report filed widget, app or email
  2. Evidence attached log, screenshot, recording
  3. AI drafts the ticket categorized, severity suggested
  4. PR linked status flows from code
  5. Resolved evidence archived with it

See a report land as a ready-to-triage ticket in minutes

Reporters need no account and no instructions. Your developers open the ticket and everything they need to reproduce the bug is already attached.