SnagRelayDocs

Introduction

What SnagRelay is, how a report travels from your site to your coding agent, and where to start.

SnagRelay turns "something is broken on this page" into a report your coding agent can act on. A small widget (or SDK) captures what happened the moment someone spots a problem: the element they pointed at, console errors, failed network requests, a session replay, and the page's environment. The report lands in your SnagRelay inbox, and your agent in Cursor, Claude Code, or Codex reads it over MCP, proposes the fix, and marks the report resolved.

Whoever finds the bug shouldn't need any technical knowledge to report it. Whoever fixes it shouldn't need to ask "can you send me more details?" ever again.

How it fits together

  1. Create a project in your dashboard. Pick a website, a WordPress site, or a React Native app.
  2. Install the report button. One script tag, the WordPress plugin, or the React Native SDK. See Installation.
  3. Connect your agent. On the project's Agent tab, add SnagRelay to Cursor, Claude Code, or Codex and approve it in your browser.
  4. Someone reports a bug. They click the report button, point at the broken element, and describe it. SnagRelay attaches the selector, errors, network calls, and replay.
  5. The report arrives in your inbox with a short key like SHOP-12. Ask your agent to fix it. It reads the full context, proposes the change, and marks the report resolved.
  6. The reporter hears back. If they left an email, SnagRelay tells them when it's fixed. See Closing the loop.

Your tracker is optional

Every report stays in the SnagRelay inbox. If your team lives in Jira, Linear, Trello, GitHub, GitLab, or Azure DevOps, connect it on the Delivery tab and each report also opens a ticket there. See Delivery.

On this page