Three ways in.
One complete bug report, every time.

Every capture — replay, console, network, and repro steps, masked in-browser — lands in your tracker the same way. The only choice is how people start one: an always-on pill, a quiet launcher in production, or your own link.

The pill — always visible

Drop one script tag on a dev, staging, or UAT build and every tester sees the coral pill on every page. One click records the session; Stop opens the report form with the replay, console, and network already attached. No accounts, no invites — anyone on the build can file.

The launcher — production-quiet

Most bugs reach support as a sentence: “checkout is broken.” No console, no network, no steps — someone on your team spends the afternoon asking follow-up questions. In production, Snag stays out of the way as a small corner launcher (the standard feedback glyph), or renders nothing at all and opens from your own “Report a bug” link or support menu.

Your own link — wire it anywhere

Nothing is rendered on the page — wire any link, button, or support-menu item to the snippet below. The record pill appears on demand, then hides again after the report. Perfect when you already have a "Report a bug" entry point.

See the whole loop run.

Plant a real bug, capture it, and watch the ticket land — 60 seconds, on the home page.