Automated visual review with an AI judge

A diff tool tells you *that* pixels changed. It cannot tell you *whether* the change was the point of the pull request or a mistake. On a busy repo that leaves you a review queue full of intended changes to click through one by one. Unlike a plain diff tool that only shows that pixels changed, UI Verify runs an AI judge over every changed story to do that triage first.

For each changed story it looks at three things - the baseline, the candidate, and the diff - and produces a verdict: a likely regression, or a likely intended change, with a short reason. Regressions surface at the top of the queue; intended changes are pre-sorted so accepting them is a single action.

The judge never changes a baseline on its own. It ranks and explains; promoting a candidate to a baseline is always an explicit action, taken by a human or by an agent you authorized. A green build never means the AI quietly accepted something for you.

Before a change reaches your queue at all, UI Verify checks it is real by re-rendering the story - a diff that does not reproduce is auto-ignored as a flake, so the judge and your review only spend time on changes that actually happened. See automatic flake detection.

Because the diffs and verdicts are exposed over MCP, your coding agent can pull them straight into the pull-request flow - list the changes, read the judge's reasoning, accept the intended ones - without you leaving the terminal. See Triage with your agent.