My Agent Swore It Fixed the UI. The Button Disagreed.

Description and use

Pawprint enables rapid visual verification of UI changes, protecting unreleased content and preventing false confidence from CI checks.

Problem

CI green checks cannot detect UI regressions such as off‑screen buttons or visual mismatches, leading to false confidence that a change is fixed.

Outcome

Pawprint enables rapid visual verification of UI changes, reducing reliance on local testing and preventing hidden regressions.

Workflow

• 1. Agent reports UI fix and passes CI checks.
• 2. Agent publishes evidence via Pawprint: description, change list, before/after comparison, screenshots/video.
• 3. Reviewer opens PR, clicks Pawprint link, reviews evidence within ~10 seconds.
• 4. Evidence is stored behind GitHub authentication, protecting unreleased app content.
• 5. Reviewer confirms visual correctness or requests changes.

Evidence

Your CI is blind. It knows the function returns true. It has no idea the modal now covers the whole checkout page, or that "dark mode fix" means white text on a white background.

Source

With Pawprint, the agent publishes evidence for the change and links it in the PR. Each publish has: a description of what changed, the list of changes, before and after comparisons, side by side, screenshots and video when a still frame isn’t enough.

Source

Agents screenshot everything, and everything includes your unreleased app. So the evidence sits behind GitHub sign‑in. Share it with your org and the people in it can see it.

Source