Igor
When an agent writes the code, you ship faster, and you meet the bugs faster too. The bugs are rarely syntax errors. They are mismatches that only appear with real data: a response shaped differently than the component expects, a missing null guard, an edge case the prompt never mentioned. Your users find them first.
The question is how quickly a report from a user becomes a fix. Most teams lose the time between the two, not in the fix itself.
Where the time goes
A user writes "checkout is broken." Someone asks which page, which account, which browser. The answer comes back a day later. Then a developer, or an agent, searches the repo for the right file. None of this is fixing. It is finding out what to fix.
The short loop
- The user points at what is wrong. They click the element. The report records its label, component and selector, and outlines in red the elements tied to an error or a failed request.
- The report carries the evidence. Console errors with file and line, requests with their bodies, repro steps and a replay of the moments before.
- The agent reads it by key. In Cursor, Claude Code or Codex, you say fix SHOP-142. The agent calls
get_issue_context, andget_issue_payloadwhen it needs one full body. - The agent fixes it and resolves it.
mark_issue_resolvedcloses the report. - The user is told. The person who reported it gets a "fixed" email.
Why the element matters most
An agent that is told "the checkout button is broken" searches broadly. An agent that is handed the element, its component and the request that returned a 422 goes to the file. The same evidence helps a human too, but an agent cannot ask a follow-up question, so what is missing from the report stays missing.
What to set up
- Add the widget to staging and production: one script tag. See the install guides.
- Connect the MCP server to your agent once. See the MCP server.
- Keep reports in the inbox, or send them to your tracker.
Learn from the last one
Reports about the same problem are grouped, and get_related_history gives your agent earlier bugs like it and the changes that fixed them. See related reports and history.