Triage visual changes from your coding agent

If an agent wrote the pull request, an agent can review the visual changes. UI Verify exposes builds over the Model Context Protocol, so a coding agent - Claude Code, Cursor, or any MCP client - can pull a build's changes into the conversation, look at each diff, read the AI judge's reasoning, and accept the intended ones.

• List a build's changed stories.
• Fetch a diff image and the AI judge's verdict for any story.
• Bucket changes into real regressions vs cosmetic reflow vs rendering noise.
• Summarize the real regressions into a PR comment.
• Accept baselines in bulk once you have signed off on the direction.

1. The agent opens the pull request and the UI Verify check runs.
2. The agent lists the build's changes over MCP.
3. It reads each diff and the judge's verdict.
4. It accepts the intended changes, and flags anything it cannot attribute to the diff for you to look at.

The bottleneck on an agent's pull request is verification, not authorship. Putting the diff and a verdict where the agent already works closes the loop: the same place the code was written is where its pixels get checked, with no context switch to a dashboard in the middle.