What Flawsnap does

Each report arrives with the proof: what was on the screen, what the console said, which calls failed and the device it happened on. Then your team works it to done.

• Screenshot annotation for bug reports

  Box, arrow, draw, text, blur and crop on a screenshot of the page, sent straight to your board.

• Screen recordings that show how the bug happened

  A replay of up to five minutes with readable steps and masked typing, attached to the report (Pro).

• Console and network logs, attached to every report

  The last 100 console messages and network calls with status and timing, never bodies.

• Device and browser details, filled in for you

  Browser, OS, viewport, language, time zone and page, plus your own metadata, on every report.

• A Kanban board where bug reports become work

  Reports become cards on a six-list board whose stages keep report status in sync.

• Insights: what happened before anyone reported it

  Journeys, screen timing, API latency and grouped errors, cookie-free, with DNT respected.

• Project docs that live next to the bugs

  Specs, test plans and release notes in the project, with mentions, share links and card links.

• AI agents that read the report and work the fix

  Claude, ChatGPT and coding agents read reports and move cards over MCP, on Pro.

• In-app bug reporting for Flutter apps

  Shake-to-report for iOS and Android Flutter apps, from the flawsnap package on pub.dev.

• Team roles, invites and project access

  Owner, admin and member roles, email invites, per-project access and widget sign-in.