DocsSnag
Capture and triage bugs with Snag
A Snag bug carries what a person saw and what the browser knew at that moment, so whoever fixes it, a developer or a coding agent, starts from evidence instead of questions. This page says what each way of reporting captures, how a bug moves across the board, and how it reaches the person or the agent fixing it. For a first session from registration to a filed bug, see Report your first bug.
From the browser#
The Chrome extension works in Chrome and in other Chromium browsers that support Chrome extensions, such as Edge and Brave. Open the page where the bug happens and click the Snag launcher on the page, or the extension's icon.
- Screenshot: a region or the full page. Mark it up before you file: circle the problem, blur what should not be shared.
- Recording: up to 90 seconds of the tab, for a bug that only shows in motion. You can pause and draw into the video; the player marks every click and failed request on the timeline.
- Context, attached for you: the page and browser, the last clicks and navigations, console errors and failed network requests. The extension keeps these in memory while you browse, so there is nothing to collect by hand.
Give the bug a title, pick the project, and file it.
From a phone#
On Android, install Snag from Google Play and share a screenshot or a screen recording into it from any app, through the share sheet. On iPhone, request the TestFlight beta from Settings, then Extension & apps. A bug filed from a phone lands in the same project as one filed from the browser.
On the board#
Every project has a board of its bugs.
A new bug arrives in Inbox with its reference, such as ANA-12: the project's three-character key and a number.
Columns run from Inbox through Triaged, In progress and Fixed to Verified and Closed; closed and rejected bugs fold away.
Triage happens on the card: severity, assignee, labels and a release. Opening a bug shows the screenshot or recording, the page and browser, the trail of steps, the console errors and the failed network requests.
Who can do what#
- A member works on the board: triage, assign, change status.
- A reporter, such as a client tester, files bugs and sees only their own. People who only file bugs are free and never count against a plan's members.
To the person or the agent fixing it#
- Slack: Settings, then Integrations, connects a workspace channel; each project can post to its own.
- A coding agent: Claude Code, Codex, Cursor or any MCP client reads a bug with all of its evidence through the TestFinch connector, fixes the code, and marks the bug fixed. Set up with your coding agent walks through it step by step.
- A test that keeps it fixed: with FlowQA in the workspace, a bug can be reproduced as a test from the trail Snag captured, and that test runs after every deploy. See Create your first test.
When the fix lands, the reporter verifies it: Verified closes the loop, and a note sends the bug back to the team.