Report your first bug with Snag
This is the first ten minutes with Snag: an account, a project, the browser extension, one captured bug, and what the team sees. Nothing here needs a desktop install.
1. Sign in
Open the Snag app and sign in with your work email. There is no password: the email you receive carries a sign-in link, and the phone apps use the six-digit code from the same email. The first sign-in creates your account.
2. Make a workspace and a project
A workspace is your team; a project is one product or site inside it.
On first sign-in Snag asks for a workspace name, then a project name.
A project gets a short key (three letters) that prefixes every bug's reference, such as SHP-12.
Invite teammates later from Settings, then Members and invites; a reporter can file bugs without seeing the board.
3. Install the extension
Settings, then Extension and apps, links to the Chrome Web Store listing. Chrome, Edge, Brave and other Chromium browsers install it the same way. After installing, open the extension and choose Sign in; it opens the Snag app once to connect, and from then on it knows your workspace and projects. On Android, install Snag from Google Play and share a screenshot or a screen recording into it from any app. On iPhone, request the TestFlight beta from the same settings page.
4. Capture a bug
Open the page where the bug happens and click the Snag launcher the extension adds to the page, or the extension's icon. Choose a region, the full page, or record up to 90 seconds of the tab when the bug only shows in motion. While you browse, the extension keeps the last clicks and navigations, console errors and failed requests in memory; they are attached automatically, you do not have to collect them. Mark up the screenshot if it helps (circle the problem, blur what should not be shared), give the bug a title, pick the project, and file it.
5. What the team sees
The bug appears in the project's Inbox column with its reference. Opening it shows the screenshot or recording, the page and browser, the trail of steps that led there, the console errors and the failed network requests from around the capture. Triage happens on the card: severity, assignee, labels, a release. Columns run from Inbox through In progress and Fixed to Verified and Closed.
6. Next
- Tell Slack: Settings, then Integrations, connects a workspace channel; each project can post to its own.
- Give your coding agent the tracker: Settings, then MCP, has the connection details for Claude Code, Cursor and other MCP clients; the agent reads the bug with its evidence and marks it fixed.
- Prove the fix: with FlowQA in the workspace, a bug can be reproduced as a test from its trail, and the test keeps running after every deploy. See the FlowQA first-test guide.