UI Verify

For coding agents

Merge agent-written UI with confidence

Your agents write the code. Seeing what they changed is the hard part. UI Verify shows exactly what every pull request changed, so your agent can fix its own regressions and you can merge without second-guessing.

Claude CodeCodexCursor

Agents ship fast. UI Verify keeps them honest.

A loop that turns agent-written UI from a review bottleneck into a few steps: your agent does the grunt work, and you still approve the merge.

See how the AI judge decides
01

Your agent ships UI

You ask for a feature, the agent writes it and opens the pull request. Same flow as a teammate, at agent speed, and UI Verify starts capturing the screens the change touches the moment the PR goes up.

dev@shoppy - claude - 92×34
> emphasize the Add to cart button on the product page
⏺ I’ll restyle the Add to cart button so it stands out more on the product page.
⏺ Update Button.tsx
  ⎿  gave the Add to cart button a bolder new style
⏺ Bash gh pr create --title "Emphasize the Add to cart button"
  ⎿  pushed emphasize-add-to-cart, opened PR #1
✓ PR #1 open · checks running, UI Verify capturing
02

UI Verify reviews it on the pull request

Every changed screen gets a verdict from the AI judge: intended, regression, or flake, with the reasoning. A real regression fails the check and blocks the merge, right there on the PR.

Emphasize the Add to cart button #1

Openagent wants to merge into main from emphasize-add-to-cart
ui-verifybot commented now

Visual changes · 2 to review

1 intended change, 1 likely regression across 6 snapshots.

components/Button Intended
pages/Product Likely regression

Review in the dashboard →

Some checks were not successful
ui-verify / visual1 regression blocks the mergeDetails
03

The agent fixes its own regression over MCP

Ask why the check failed. Over MCP the agent pulls the build, reads each verdict, fixes what it broke, and re-runs to green. What reaches you is a small set of decisions, and you still approve the merge.

dev@shoppy - claude - 92×34
✻ Welcome to Claude Code
cwd: ~/projects/shoppy
model: Sonnet 5 · uiverify (MCP) connected
> see why the PR checks failed
⏺ The UI Verify visual check failed. Let me pull what I changed on the UI.
⏺ uiverify - get_diff (MCP)(build: "#1")
  ⎿  2 changed: components/Button, pages/Product
⏺ Two changes. The Button restyle on its own is intended.
  But on the product page the Add to cart button is now a faint outline - that one is not.
⏺ Fixing: keep the new style, restore the button’s fill and text.
⏺ Update Button.tsx
  ⎿  restored the solid fill, re-ran the check
✓ re-run passed · 0 regressions · ready to merge

Connect the UI Verify MCP

One command connects any MCP-compatible agent, like Claude Code, Codex, or Cursor. Your project setup page has it with the key already filled in.

  • List the builds on a branch or pull request
  • Inspect each changed snapshot and its overlay
  • Read the AI judge's verdict and reasoning
  • Accept the intended changes or deny a regression
  • Push the fix, all without leaving the terminal
dev@shoppy - zsh - 92×34
$ claude mcp add --transport http uiverify \
https://uiverify.ai/api/mcp \
--header "Authorization: Bearer YOUR_UIVERIFY_API_KEY"
✓ Added HTTP MCP server uiverify

Your agent installs it

Create a project and paste one prompt into your coding agent. In about five minutes it reads the docs, writes the workflow, wires your capture, and opens the first PR. You just drop in your API key.

dev@store - claude - 92×34
> set up UI Verify visual testing in this repo
⏺ I’ll read the setup guide and wire it into your CI.
⏺ Fetch uiverify.ai/llms.txt
  ⎿  read the setup guide + capture scoping
⏺ Detected Storybook. Adding the workflow and capture step.
⏺ Write .github/workflows/visual.yml
  ⎿  runs on every PR, uploads the Storybook build
⏺ Last step: add your UIVERIFY_API_KEY secret from your project.
✓ opened a PR · first build is running

Let your agents review their own UI

Start free in minutes, no credit card. Or book a demo and we’ll get you live in your CI.