Snag by TestFinch

Bug reports a developer or an agent can act on

One click in the browser extension captures the page, a screenshot you can mark up, the last steps, console errors and failed network requests. The board keeps the team honest about what is open, and a coding agent reads the same snag over MCP with the evidence in hand.

Open Snag Install the extension

Free for one project and fifty snags a month. Sign in with your email and a six-digit code.

A filed snag with its screenshot, the page it was captured on, the console error and the failed request. — A filed snag: screenshot, trail, console and network, as the extension captured them. Sample data.

01Capture

Everything a fix needs, captured at the moment it broke

The extension keeps the last clicks and navigations, the console and the network in memory while you browse. When something is wrong, one click files it with the page, the screenshot and a trail that says how you got there. When a screenshot is not enough, record up to 90 seconds of the tab with the same context attached. The mobile app does the same from a phone, and a share sheet files a screenshot or a recording from any app.

Mark up the screenshot: Circle the problem, blur what should not be shared, and the annotated image is what the team sees first.
Record when it moves: Up to 90 seconds of the tab, with pause and a pen that draws into the video. The player marks every click and failed request on the timeline.
Triage that stays light: Severity, assignee, labels, releases and a stale filter. Columns from inbox to closed; closed and rejected fold away.
Where the team already is: Slack notifications, ClickUp tasks, Sentry events on a snag's backend tab.
One workspace with FlowQA: Reproduce a snag as a FlowQA test from its captured trail; a failing test files its own snag back.

02The board

What is open, who has it, how old it is

Cards carry severity, assignee, labels and how many FlowQA tests cover them. The dashboard shows the pipeline, the verification backlog and ageing, per project.

A Snag board with columns from inbox to verified and cards carrying severity and assignee. — A Snag project board.

03For coding agents

Give your agent the bug tracker

Connect Snag to Claude Code, Cursor or any MCP client. The agent lists what is open, reads a snag with its screenshot, console and network, fixes the code, and marks the snag fixed with a note. With FlowQA in the workspace it can also run the covering tests before it says done.

Open Snag Pricing