Teams on GitLab usually have the opposite of a tooling problem: the issues are in one place, the bug reports in another. A report in chat or email turns into an issue only when someone retypes it, and the evidence is lost on the way.
What SnagRelay does
A report from the widget becomes an issue in your GitLab.com project, with the following attached:
- the element the reporter pointed at, with errors tied to it
- console errors with file and line
- requests with request and response bodies, failed and successful
- repro steps and a short session replay
- browser, OS, viewport and URL
A screenshot with markup is attached as well, on every plan. See pricing.
SnagRelay supports GitLab.com. Self-managed GitLab is not supported.
Setting it up
- In your SnagRelay project, choose GitLab as the tracker and authenticate your account.
- Choose the project that receives issues.
- Add the widget to your site with one script tag. See the install guides.
- Report a test bug and check the issue.
A project sends to one tracker, or to the SnagRelay inbox. Use separate projects for separate GitLab destinations.
Without and with
| Without | With SnagRelay |
|---|---|
| Report lands in chat or email | Report lands as an issue |
| Someone retypes it | Nothing to retype |
| Developer asks for console output and the request | It is in the issue |
| Nobody tells the reporter it was fixed | Resolving the report emails them |
Fix it from your agent
Connect the SnagRelay MCP server to Cursor, Claude Code or Codex. Say fix and the issue key; the agent reads the element, errors and requests with get_issue_context, and resolves the report with mark_issue_resolved.
Who it suits
- Teams on GitLab.com who collect bugs from testers or clients
- Teams whose developers already work with a coding agent
- Agencies who report on client sites, where the reporters have no GitLab account
Igor