// Platform — Detected issues
The bugs nobody reports. Caught anyway.
Opt in and Rebase collects uncaught exceptions and unhandled rejections from every visitor session — into a staged review queue. Nothing becomes a ticket until a human promotes it.
Turn it on
Off by default. Owners opt in per project, and from then on every visitor session is covered.
Errors group themselves
Each distinct error is fingerprinted into one row — occurrence count, first and last seen, sessions affected.
Promote what matters
One click turns a candidate into a real ticket — through triage, source attribution and your tracker.
// A queue, not a flood
One row per problem.
Errors land in a staged queue — not your ticket list, not your tracker. The same error on five routes is one row listing five paths, with a 14-day daily trend behind it.
- Grouped across pages — five routes, one row
- The trigger recorded: the last user action before the crash
- Occurrence counts, first/last seen and sessions affected
Detected issues · acme.comqueueTypeError: cart is undefined — checkout.js
no ticket yet — your call
// Human in the loop
Promote, snooze or mute.
Promoting a candidate creates a real ticket that flows through the entire pipeline — AI triage, source attribution, tracker issue. Everything else stays quietly out of the way.
- Snoozed errors resurface after 10 more occurrences
- Muted errors stay silent for good
- Dismissed items clean themselves up after 30 days
[Rebase] TypeError: cart is undefined
through the full pipeline
// The details
Proactive, not noisy. By construction.
- Off by default — owners opt in per project
- Uncaught exceptions and unhandled promise rejections, auto-collected
- Covers the users who would never click 'report'
- Fingerprinted and collapsed — one row per distinct error
- Symbolicated stacks from the 2nd occurrence, matched to your repo
- The widget throttles itself: max 10 reports a minute, deduped twice
- The queue caps at 200 active items with automatic pruning
- Promoting twice returns the same ticket
Frequently asked questions
No. Detected errors land in a staged review queue — not your ticket list, not your tracker. Nothing becomes a ticket or a tracker issue until a human promotes it, and snooze and mute keep the queue quiet.
No. Proactive detection is off by default; owners opt in per project. Once enabled, it runs on every visitor session.
It becomes a real ticket that flows through the entire pipeline — AI triage, source attribution and a tracker issue. Promoting the same candidate twice returns the same ticket.
The widget throttles itself to 10 reports a minute and dedups client-side, the server dedups again, and the queue is capped at 200 active items with automatic pruning. A storm can't take you down.
// Keep exploring
The rest of the platform. It all works together.
Capture
Click to report — console, network, steps & a screenshot.
Triage & AI
Summary, severity & the suspected file — evidence-linked.
Collaboration
Pins on the live page — threads, mentions & roles.
Issue-tracker sync
Files into GitHub, Linear, Jira & Asana. Two-way status.
AI agents (MCP)
Five MCP tools with scoped, revocable tokens.
Team & notifications
Invites, roles, unlimited users — mentions instant, the rest digested.
Privacy & security
Masked by default, scrubbed twice, isolated per tenant.
Start shipping feedback faster.
Start your 7-day free trial.