FAQ

Is SnagRelay a developer tool?

It's installed by developers (one script tag) but built for the people who report bugs — QA engineers, testers, PMs, clients, and end users. The goal is for every report to arrive with enough context that developers never need to ask for more.

Do reporters need technical knowledge?

No. Reporters click the widget, annotate a screenshot, describe the issue, and send. SnagRelay automatically captures the technical context — page state, console errors, network data, and browser/device info.

Do I need to use a separate issue board?

No. Reports go directly into the tracker you already use — Jira, Linear, Trello, GitHub, GitLab, or Azure DevOps. The dashboard is for setup and configuration, not day-to-day bug triage.

Can I run separate staging and production setups?

Yes — create a separate Project for each. Each gets its own API key and its own tracker connection, so a bug filed on staging doesn't land in your production queue. There's no built-in environment switch within a single Project.

No. It loads asynchronously and only becomes active when a visitor opens it — it has no measurable impact on page speed or Core Web Vitals.

Can I remove the "Powered by SnagRelay" watermark?

The watermark only appears on the Free plan. It's removed automatically on Studio and Agency.

The web widget is what actually captures and submits reports. The Chrome extension is an optional companion that improves screenshot quality on Chromium browsers — it does nothing by itself.

What's the difference between the VS Code extension and the AI Agent?

The VS Code / Cursor extension is the editor UI; MCP is the underlying protocol it (and other AI-enabled editors) use to talk to SnagRelay. Both require the Agency plan.

Does SnagRelay support team seats or SSO?

Not currently — SnagRelay accounts are single-owner. "Team Members" shown inside a Project are synced from your connected issue tracker, not SnagRelay seats.