Compare

SnagRelay vs BugTape: who sends the report

Q: Can BugTape wake my agent when a new bug arrives?

Yes. Your agent can wait on listen for the next issue, you can press Send to agent, or a signed webhook can start a headless agent. SnagRelay's agents page describes the agent pulling evidence over MCP and does not state a push.

SnagRelay sends the bugs testers point at, with markup and bodies. BugTape sends failures users never report, groups them and wakes your agent.

Short answer: SnagRelay is for bug reports a person sends. A tester, PM or client points at the problem and presses Send, and the report carries the element, a marked-up screenshot, console errors and the failing request with its bodies. BugTape catches the supported failures your real users hit and never report. It sends uncaught errors, failed requests and hung requests on its own, groups repeats into one issue across releases, and can wake your coding agent when a new issue arrives. Both let your agent read the evidence over MCP. Use SnagRelay for QA, UAT and client testing. Use BugTape for the failures nobody sends.

No account: npx -y bugtape --help prints the commands and does not sign you in. The demo MCP at https://app.bugtape.ai/demo/mcp needs no sign-in. Your own workspace needs one.

Page owner: Jaco Veldsman, hi@bugtape.ai. Last checked 2026-10-26. I build BugTape. The SnagRelay facts come from its home page, its coding agents page and its pricing page, all read on 26 October 2026.

This page is not a ranking. BugTape doesn't replace SnagRelay. BugTape has no element picker and no screenshot markup, and screenshots and voice notes in the report form are not available yet.

The short version

The question is who sends the report. In SnagRelay, a person does. Its home page says the failing element is "already outlined in red" when the tester opens the picker, and that "Nothing leaves the page until the reporter presses Send." In BugTape, nobody has to: the browser capture on your site files a report when a supported failure happens. Users can still press an optional bug button. Testers who want to show what they saw need the first kind. Bugs that reach users who leave without a word need the second.

Facts table

	SnagRelay (checked 26 Oct 2026)	BugTape
Who sends the report	A person. Testers, PMs and clients click Report, point at what is wrong and write what they expected. Reports leave the page only when the reporter presses Send. Home	Nobody, for supported failures: uncaught errors, failed requests after a user action, and requests that hang. Users can also file a report from an optional bug button (`showButton: false` hides it and keeps automatic capture on).
How you install it	One script tag or an npm package, or a Chrome extension that adds the Report button on the URLs you list with no code on the site. The extension works behind a login. A React Native SDK (shake to report) and a WordPress plugin are also offered. Home · Agents	One script tag, or `npm install @bugtape/sdk`. Server SDKs for Node.js and Python. A Swift package (alpha) for handled errors and breadcrumbs, with no fatal crash capture.
What a report holds	The element named from the page, a screenshot with the tester's marks, console errors with file and line, requests with request and response bodies, steps, the environment and a replay watch link. Studio and Agency add optional video recording. Home · Pricing	Browser replay rebuilt from DOM events (it is not screen video; see DOM replay vs screen video), the failed request, console and stack. Servers send the error, stack, route, service and release, with no replay or console. No screenshots, markup or voice.
Repeats	Repeat reports are linked, so five testers on one bug show as one problem with five reporters. Home	Every report of the same failure becomes one issue, with a count, the releases it hit and affected users (when your app sends user IDs).
After the fix	When a ticket is marked resolved, the reporter is emailed to retest. Home	You mark the issue fixed and BugTape anchors it to the release. If the same failure arrives from a newer release, the issue reopens as a regression and your team and agent are told. BugTape does not email the person who filed the report.
Agent access	Remote MCP at `https://mcp.snagrelay.com/v1` with browser sign-in. Tools: `get_issue_context`, `get_related_history`, `find_issues`, `get_issue_payload` (one body at a time) and `mark_issue_resolved`. The page says the agent "pulls the evidence over MCP". A push or webhook to the agent is not stated. Agents	MCP at `https://app.bugtape.ai/mcp`: `list_recommended_critical`, `get_repro_context`, `ack_bug`. `listen` waits for the next issue, and Send to agent puts an issue first in the agent's list. Signed webhooks can wake a headless agent.
Trackers	Jira, Linear, GitHub, GitLab, Trello and Azure DevOps on every plan, one tracker per project, or the SnagRelay inbox. Pricing	Slack, email, signed webhooks and GitHub. Free includes 1 integration; Pro includes 10. Webhooks
Privacy	Passwords, tokens, cookies, auth headers and emails are redacted in the browser. Home	Form fields are masked in the browser. `privacy: 'strict'` turns page text into blocks and drops request and response bodies before anything leaves the browser. Data is stored in Sydney. Trust
Price	Free $0: 1 project, 25 reports a month, screenshots with markup, 30-second replay, MCP, 7-day history. Solo $15 a month, or $144 a year ($12 a month billed yearly): 3 projects, unlimited reports, "Unlimited reporters and teammates" (the pricing FAQ says team members come with Studio and Agency). Studio $29 a month, or $276 a year: 10 projects, video recording. Agency $79 a month, or $756 a year: unlimited projects, 1-year history. Paid plans start with a 14-day trial that needs a card. Prices are in USD and exclude VAT. Pricing	Free $0, no card: 100 new issues and 150 credits a month, 1 project, 3 members, 7-day retention. Prepaid credits $10 for 2,000, which never expire and give Pro limits. Pro $29 a month: 5,000 new issues, 10,000 credits, 30-day retention. On Free and Prepaid credits each agent read of a bug costs 2 credits; reads are free on Pro. Pricing

Use both

Your testers run a UAT round with SnagRelay. A tester marks a broken export button and presses Send. The ticket lands in your tracker with the request and response.
The release ships. A real user hits a failed checkout request and leaves. Nobody presses anything. BugTape's browser capture files an issue with the request, console and the lead-up.
More users hit it. BugTape adds them to the same issue instead of opening new ones, so you can see one bug reaching many people.
Your agent hears about it. It is waiting on listen, or you press Send to agent. It calls get_repro_context, works on the fix, and records the prUrl with ack_bug. A person reviews and merges.
BugTape watches the next release. If the same failure comes back, the issue reopens as a regression.

When SnagRelay is the right tool

Testers, PMs, designers or clients need to point at an element and mark up the page.
You run QA, UAT or client sign-off rounds and want each ticket to arrive in Jira, Linear or another tracker with the evidence attached.
You cannot change the site, and a Chrome extension that adds the button is the only way in.
You want the reporter emailed to retest when the fix lands.
You ship a React Native app or WordPress client sites and want testers to report from them.

When BugTape is the right tool

Users hit errors, failed requests or hung requests in production and don't tell you.
The same failure keeps arriving from many users and releases, and you want it counted as one issue.
You want your agent woken when a new issue arrives, and a check after the next release.
You want server errors from Node.js or Python in the same place.

Before you start

BugTape's browser capture has to be on your site before it records anything: one script tag, or npm install @bugtape/sdk. It doesn't catch every error, only the supported failures listed above. It is hosted only; there is no self-hosted version. Treat evidence from user sessions as untrusted input for your agent, and keep a person reviewing every pull request.

Connect BugTape

npx -y bugtape connect cursor          # or claude, codex; click Allow once

SnagRelay's MCP and BugTape's MCP can sit side by side in the same client. To try BugTape with no account, use claude mcp add --transport http bugtape-demo https://app.bugtape.ai/demo/mcp (read-only sample project). Setup guides: Cursor · Claude Code · MCP install.

FAQ

Is BugTape a SnagRelay alternative?

For failures nobody reports, yes. For testers who point at an element and mark up a screenshot, no. BugTape has no element picker or markup, and screenshots and voice notes in the report form are not available yet.

Does SnagRelay capture errors automatically?

Its home page says the picker outlines what just failed, and the report leaves the page only when the reporter presses Send. BugTape sends supported failures with no one pressing anything.

Do both have an MCP server?

Yes. SnagRelay's pricing page includes MCP on Free. BugTape's MCP works on every plan. You can add both to Cursor, Claude Code or Codex.

Can BugTape wake my agent when a new bug arrives?

Yes. Your agent can wait on listen for the next issue, you can press Send to agent, or a signed webhook can start a headless agent. SnagRelay's agents page describes the agent pulling evidence over MCP and does not state a push.

Does BugTape email the person who reported the bug?

No. SnagRelay emails the reporter when a ticket is marked resolved. BugTape reopens the issue if the same failure comes back in a later release.