What is SnagRelay?
A quick overview of what SnagRelay does and who it's for.
SnagRelay captures the page state, the element, console errors, failed requests, and a session replay the moment someone reports a bug. Your coding agent then reads that report over MCP, so the fix starts from evidence instead of a vague description.
Who reports bugs
Anyone. No dashboard account and no technical knowledge needed. A reporter clicks the report button, points at what's wrong, writes a sentence or two, and sends it.
- You and your team while building and testing
- QA engineers and testers running through test plans
- Clients reviewing a staging build
- End users, if you choose to show the widget publicly
Reporters who leave an email are told when the bug is fixed.
Who fixes bugs
Your coding agent, with you in the loop. Cursor, Claude Code, and Codex connect to a project over MCP, read the report, and propose the change. If your team also works in a tracker, each report can open a ticket there too.
What gets captured
| Capture | Free | Solo | Studio | Agency |
|---|---|---|---|---|
| Element picker (selector, text, location) | ✓ | ✓ | ✓ | ✓ |
| Console errors and warnings | ✓ | ✓ | ✓ | ✓ |
| Network requests with response bodies | ✓ | ✓ | ✓ | ✓ |
| Reproduction steps | ✓ | ✓ | ✓ | ✓ |
| Session replay | 30 s | 60 s | 60 s | 3 min |
| AI-written title | ✓ | ✓ | ✓ | ✓ |
| Screenshots and markup | ✓ | ✓ | ✓ | |
| Video recording | ✓ | ✓ |
See Plans & Limits for projects, report volume, history, and the rest.