Installation
Installation Overview
Pick how the report button gets onto your site or app: script tag, WordPress, React Native, or the Chrome extension.
Each project has one install channel. Choose it on the project's Install tab. The tab shows your real snippet, your API key, and a live status that turns green once the widget loads.
| Channel | Where it runs | How it authenticates |
|---|---|---|
| Script | Any website or web app | Project API key in the page. Optionally hidden until an invited reporter unlocks it |
| WordPress | WordPress sites | Project API key in the plugin settings |
| React Native | iOS and Android apps (Expo Go, dev client, or bare) | Project API key in .env as EXPO_PUBLIC_SNAG_RELAY_API_KEY |
| Chrome extension | Matching hosts in Chrome, Edge, and Brave | Owners Sign in as owner. Invited people Authenticate with email and a 6-digit code |
To fix reports rather than file them:
| Client | Role |
|---|---|
| Connect your agent | Cursor, Claude Code, and Codex read reports over MCP |
Which channel should I pick?
- A website or web app you can edit. Use the script tag.
- WordPress, no theme edits. Use the plugin. Add developer context to get plugins, theme, versions, and PHP errors on every report.
- A mobile app. Use the React Native SDK. Reporters shake the device or tap the button.
- No embed on the site; people report from their browser. Use the Chrome extension (Chrome Web Store).
Chrome extension replaces the embed
Selecting Chrome extension turns off embed injection for that project. Don't mix a script tag and the extension on the same project.