From website feedback to a merged fix
The whole path from "this button is wrong" to a merged pull request, step by step, with what is free, what is Pro, and where a human stays in charge.
Step 1: capture feedback a developer can act on
The loop only works if the first report is complete. A reviewer opens the site through the embedded widget or a shareable link, clicks the element they mean, and writes what should change. No account is needed. The report saves the CSS selector, tag and text of the element, a screenshot, recent console errors and network calls, the page URL and viewport, and a DOM replay of the last couple of minutes. On React and Next.js sites with the SDK, it also names the component and the source file:line that rendered the element, so nobody has to ask where it lives.
Step 2: triage the queue
Every project has its own pipeline, so one client or product never mixes with another. Items move across a kanban board from new to done, and the Free plan can export new items to GitHub Issues automatically. On Pro, AI classifies each item by sentiment, intent (bug, feature or UX) and urgency, so an angry report about a broken checkout rises above a request to change a font. Triage is where a person decides which items are worth fixing, before any code is touched.
Step 3: hand the item to a coding agent
On any plan, one click turns an item into a ready-to-run Claude Code prompt with the source mapping included. Teams that work in Cursor, Claude Code or VS Code can connect the Feedback DevTools MCP server instead: the agent lists open feedback, reads one item with its full context, claims it so two agents never work on the same report, makes the change in your local checkout, and marks the item resolved with the pull request URL. The agent uses your own repository access, so Feedback DevTools never needs push rights for this path.
On Pro, Autopilot can take the item instead. It is switched on per project and needs a GitHub token with Contents and Pull requests write access. Once an item is approved, the agent clones the repository, makes the change, pushes a branch and opens the pull request. If the project deploys previews on Vercel, Feedback DevTools re-shoots the same element on the preview so the pull request carries a before and after screenshot. Autopilot opens pull requests; it never merges them.
Step 4: review, merge and close the loop
A person reviews the pull request and merges it, the same as any other change. When a pull request opened by an Autopilot run merges, GitHub tells Feedback DevTools and the item moves to done on its own; when your own agent made the fix, it marks the item resolved with the pull request URL. If the project has a public portal, shipped items appear on the project changelog, published as a web page, as Markdown for agents and as an RSS feed, so the reviewer can see the change shipped without a status email.
For problems the widget detects on its own, such as a repeated error on one element, Feedback DevTools also checks whether the fix held. When an Autopilot pull request for one of those merges, it compares how often the same signal appeared in the seven days before the merge with the 72 hours after it, and comments the verdict on the pull request: verified, improved or regressed. With too little traffic to tell, it says nothing. Human-written feedback is not scored this way; its proof is the reviewer seeing the change.
Frequently asked questions
Can website feedback turn into a pull request automatically?
Yes, on the Pro plan with Autopilot switched on for the project. After you approve an item, the agent opens a pull request with the change and, on Vercel preview deploys, a before and after screenshot. It never merges; a person reviews and merges every pull request.
What does the free plan include in this loop?
Capture with screenshot, console and network context, the kanban pipeline, automatic export to GitHub Issues, CSV/JSON export, one-click Claude Code prompts and the MCP server for your own coding agent. Autopilot and AI triage are Pro, at $9/mo per project.
Does Feedback DevTools need write access to my repository?
Only for Autopilot, which needs a GitHub token with Contents and Pull requests write access. If your own agent in Cursor or Claude Code makes the change, it uses your existing access and Feedback DevTools never pushes code.
How do reviewers find out their feedback was fixed?
Once the item is shipped, projects with a public portal list it on the changelog page, the Markdown changelog and the RSS feed. Pull requests opened by Autopilot move the item to done automatically when they merge.
Keep reading
Try it on your own site
Feedback DevTools is free to start: unlimited feedback, shareable review links and no client accounts.