Bug reports

Collect bug reports from users who would never open a support ticket.

The reports you receive today are the ones somebody cared enough to chase you about. The rest — the person who could not check out and simply left — are the ones you needed. A button on the page costs them fifteen seconds and no account, and what it sends is a bug you can reproduce.
Start freeNo credit card required.
one report, in full
"I can't apply my discount code at checkout"

Chrome 131 · macOS 15.1 · 1440 × 900 @2x · Europe/Madrid
TypeError: Cannot read properties of undefined (reading 'total')
    at CartSummary (app.4f2c1.js:284:19)

1 /cart → 2 click "Apply code" → 3 submit form#discount
Screenshot attached · Reported 2h ago

What a report carries

One sentence from them, everything else from the browser

A person reporting a bug can tell you what they were trying to do. Everything else is mechanical, and asking them for it is how you end up with “Chrome, I think, on my laptop”.

No account

The signup wall is what costs you the reports

Every step between noticing a problem and describing it removes most of the people who would have described it. A portal they must register on removes nearly all of them, and the ones who remain are your most invested users — which is a biased sample of exactly the wrong kind. If your app already knows who is signed in, pass the id you have and nobody is asked for an email either.

What this is not

Not error monitoring, and not session replay

An APM catches exceptions nobody reported, which this structurally cannot; if you do not have one, that is the gap to close first — we wrote up where the two divide. And nothing here records continuously: the steps live in the visitor’s own tab and are discarded when they close it, so the field list on the widget data page is short enough to cite in your privacy policy.

Then fix it

Hand the whole report to your coding agent

Reading a bug report is not the job. The MCP server gives Claude Code or Cursor the description, the stack frames, the browser and the numbered steps in one call, so the agent starts from the same evidence you would have — without you pasting any of it. Ideas come through the same button, into the same inbox.

FAQ

Questions

Do users need an account to report a bug?
No. They press the button on the page where it broke, type a sentence, and optionally leave an email. Requiring a signup filters for your most patient users rather than the ones who hit the worst bugs.
What arrives with a bug report?
The description, the page URL, the browser and version, operating system, viewport, pixel density, time zone, up to ten JavaScript errors with stack frames, the last fifty actions taken, and a screenshot if one was attached.
How is this different from error monitoring?
Sentry catches every exception, including thousands nobody noticed, and never knows what the person wanted. This only fires when somebody reports, and starts with what they were trying to do. Most teams run both.
Can I turn the technical collection off?
Yes, per project, with one switch. Reports then arrive with the description and contact details only — no browser, no errors, no steps. Every field is listed on the widget data page for your privacy policy.
Does it work on a single-page app?
Yes. The widget attaches to the document once and survives client-side navigation, and each route change is recorded as a step, so a report shows the real path through the app rather than one URL.

Report a bug on this page.

The widget in the corner is the real one. Send something and look at what arrives underneath your sentence.

Start freeRead the docs