Reading a Report
The full report page: what they said, replay, what happened, errors, environment, and handing it to an agent.
Click any report in the inbox to open its page. It's one long page, not a set of tabs, so the whole story reads top to bottom.
Sharing
The Share link button copies the report's public URL (/issues/{token}/report). Anyone
with the link can view the report without a SnagRelay login, so it's easy to hand to a
contractor or another team. If a tracker is connected, a button links to the ticket there.
The header has Start working and Mark done (or Reopen for a resolved report).
What's on the page
What they said. The reporter's own words, quoted. The headline above is the (optionally AI-written) title. See AI titles.
The screenshot and replay. The annotated screenshot, when there is one, and a Watch replay button with its length if a session replay was captured.
What happened. The reconstructed steps leading up to the report: navigate, interaction, observe, console, and network. See Reproduction steps.
Errors. Console errors and warnings with stack traces, and failed network requests with request and response headers and bodies where captured. Sensitive headers and token-like keys are redacted.
Hand it to your agent. A card with the report's key and one-click actions:
- the
fix SHOP-12command, to copy - Open in Cursor
- Copy for Claude Code
- No MCP? Copy the full context: the whole context as Markdown or JSON, to paste into any assistant
Environment. Browser, device, viewport, screen, language, and timezone, plus any extra technical info (for example, WordPress plugins, theme, and PHP errors from the WordPress plugin), with the user agent tucked away. Likely areas lists the components the report probably touches.
What your agent sees
The agent gets the same evidence through get_issue_context, plus related past fixes from
get_related_history. See Connect your agent.