Feedback DevTools

For QA teams

Bug reports that reproduce themselves

Half of QA is archaeology: reconstructing what the reporter saw, on which page, in which browser, with which console error. Feedback DevTools captures all of it at the moment of the click.

Every report arrives with the exact element, its React component and source file:line, console errors, failed network calls, screenshot, URL, viewport and user agent. Triage becomes sorting, not sleuthing.

Free plan included · no credit card · reporters need no account

Watch the 60s file:line demo first

How it works

  1. 1

    Share a feedback link

    Reporters need no account. Anyone with the link can click an element, annotate and submit.

  2. 2

    Every report self-documents

    Screenshot, exact element, component + file:line, console errors, failed network calls, URL, viewport and user agent — captured automatically at click time.

  3. 3

    Triage on the kanban

    New items land in a pipeline your team already understands. Pro adds AI classification by sentiment, intent and urgency so the critical ones surface first.

  4. 4

    Hand developers something actionable

    Export CSV/JSON, or let the developer pull the same source-mapped context straight into Cursor or Claude over the hosted MCP.

Why QA teams pick Feedback DevTools

  • The repro packet is automatic. Console errors, network failures, viewport, user agent and URL attach to every report — "works on my machine" dies here.
  • file:line ends the handoff tax. Developers open the exact source location instead of grepping for a button label.
  • No seats to manage. Reporters are free and unlimited — clients, beta users, support staff, all of them.
  • AI triage at queue scale. Pro sorts by sentiment, intent and urgency, so a furious blocker outranks a polite nitpick without a human reading first.
  • Your data stays yours. CSV/JSON export on every plan, including free.

See a real report before you sign up

The 60-second demo shows an actual source-mapped item: component, file:line, console error and the Claude Code prompt it generates. No account needed.

Open the demo

Agent? The same context is available over the hosted MCP: https://server-production-14a9.up.railway.app/mcp · discovery at /.well-known/mcp.json · pricing: Free $0 / Pro $9 per project per month

Frequently asked questions

What exactly is captured with each report?

The reporter’s description, a screenshot, the exact element clicked, its React component and source file:line:col (with the SDK), console errors and warnings, failed network requests, page URL, viewport size and user agent.

Do testers or clients need accounts?

No. Share a feedback link and anyone can report. Accounts are only for the team triaging in the dashboard.

Can we export to our issue tracker?

Every plan includes CSV/JSON export, so Jira, Linear or a spreadsheet import all work. Native integrations are on the roadmap.

How does AI triage help a QA team?

Pro ($9/mo per project) classifies each item by sentiment (angry/happy/neutral), intent (bug/feature/UX) and urgency. On a 200-item regression pass, the queue arrives pre-sorted.

Get early access and give your team reports that reproduce themselves.