Installation Overview
Five ways to capture bug reports, and one to fix them.
SnagRelay ships five different capture clients, plus a developer-side extension for fixing reports. Pick the ones that match where your users actually are.
| Client | Captures reports? | Where it runs | Install method |
|---|---|---|---|
| Web Widget | Yes | Any website | Script tag |
| WordPress Plugin | Yes (same widget) | WordPress sites | WordPress.org plugin directory |
| Chrome Extension | No — companion only | Chrome/Edge/Brave | Chrome Web Store |
| React Native SDK | Yes | iOS & Android apps | npm package |
| VS Code / Cursor Extension | No — for fixing bugs | Developer's editor | Marketplace / Open VSX |
The Chrome extension doesn't report bugs by itself
It's a screenshot-quality helper for sites that already run the web widget. Without the widget script installed, the extension has nothing to attach itself to.
The VS Code / Cursor extension is for developers, not reporters
It lets a developer browse reports, start a fix, and pull full context into their AI coding assistant via MCP — it doesn't capture new bug reports.
Which one should I install?
- Building a regular website or web app? → Web Widget
- Running WordPress and don't want to touch code? → WordPress Plugin
- Want higher-fidelity screenshots (across tabs, iframes, etc.)? → also install the Chrome Extension
- Building a mobile app? → React Native SDK
- A developer who wants to fix bugs from your editor? → VS Code / Cursor Extension
You can combine several — e.g. the web widget on your marketing site, the WordPress plugin on your blog, and the React Native SDK in your mobile app, all reporting into different (or the same) Project.