Introduction
What SnagRelay is, how it fits into your workflow, and where to start.
SnagRelay is a bug-reporting and QA tool. A small widget (or SDK) captures a screenshot, console errors, network activity, and a session replay the moment someone spots a problem — then delivers a fully-detailed report straight into the issue tracker your team already uses.
The pitch is simple: whoever finds the bug (a QA engineer, a PM, a client, an end user) shouldn't need any technical knowledge to report it, and whoever fixes the bug shouldn't need to ask "can you send me more details?" ever again.
Quick Start
Sign up, create a project, connect a tracker, and install the widget in under 5 minutes.
Core Concepts
Projects, Issues, integrations, and plans — the vocabulary used throughout these docs.
Installation
Web widget, WordPress, Chrome extension, React Native, and the VS Code / Cursor extension.
Integrations
Jira, Linear, Trello, GitHub, GitLab, and Azure DevOps.
How it fits together
- Create a Project in your dashboard and connect it to an issue tracker (Jira, Linear, Trello, GitHub, GitLab, or Azure DevOps) via OAuth.
- Install a capture client — usually the web widget, but SnagRelay also ships a WordPress plugin, a React Native SDK, and a companion Chrome extension for higher-fidelity screenshots.
- A user reports a bug. They click the widget button, annotate a screenshot, and submit. SnagRelay automatically attaches console errors, failed network requests, browser/device info, and — on paid plans — a session replay and reproduction steps.
- The report lands in your tracker, already formatted, with an AI-generated title and (optionally) an assignee and priority set by your triage rules.
- Developers fix it. From the VS Code / Cursor extension or the AI Agent (MCP), a developer can pull full report context straight into their editor and mark it resolved when done.
One project, one tracker
Today, each SnagRelay Project connects to exactly one issue tracker. If you run separate staging and production environments, create a separate Project (and API key) for each — see Core Concepts.