Automated visual review with an AI judge
Not every visual change is a bug. UI Verify's AI judge tells an intended change from a real regression, so your review queue is only what actually needs a human.
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 pure pixel-diff tool such as Chromatic or Percy, UI Verify runs an AI judge over every changed story to do that triage first.
What the judge does
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 advises, you decide
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.
Reviewing from your coding agent
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.
Visual testing for agents
UI Verify captures your UI on every pull request and an AI judge tells an intended change from a real regression. See how it works.
Get started