Visual testing for coding agents.
Catch UI regressions before they ship. Give your agent the screenshots your team approved and the comments that explain what changed.
$ vizzly api schema sdk.getBuildContext --json ↳ GET /api/sdk/context/builds/{buildId} · Vizzly-API-Version: 2026-09-12 $ vizzly api /api/sdk/context/builds/abc123 \ -H 'Vizzly-API-Version: 2026-09-12' -q limit=10 --json { "resource": "build_context", "build": { "id": "abc123", "status": "completed", "visual_review": { "state": "pending" } }, "summary": { "comparisons": { "total": 1, "pending": 1 } }, "evidence": [{ "type": "comparison", "id": "cmp456", "name": "checkout-empty-state", "result": "changed", "review_state": "pending" }], "page": { "returned": 1, "has_more": false } }
Your agent should know what you already approved.
A fresh screenshot shows your UI today. Vizzly also keeps the approved version and earlier review comments, so you and your agent can see what changed and why it was accepted.
Explore the workflow
A tiny reviewer with excellent glasses
The bear can point at the diff. Your team decides what ships.
Open the diff, read earlier comments, and decide whether the change belongs. Your next agent can read that review before editing the same screen.
Approved baselines
Screenshots your team has already accepted.
Changes you can inspect
See the diff alongside the route, branch, and commit.
Your review history
Keep the comments that explain an approval or rejection.
$ vizzly tdd run "npm test" --no-open
Compare locally
Run your screenshot tests and open a report of what changed.
$ vizzly api schema --json
Inspect cloud results
Discover the requests available for a cloud build.
$ vizzly run "npm test" --wait
Review with your team
Upload a cloud build and review the changes in your pull request.
Add visual regression testing to your next PR.
Run your screenshot tests, review the changes, and give the next agent a record of what your team accepted.