See every PR the way your users will.

How it works

1. 1

   Open a pull request

   When your PR gets a preview URL, Walkproof reads what the PR is meant to change (its description, linked issue and diff) and posts its test plan as a check you can correct.

2. 2

   It walks the changes and records everything

   An agent goes through each flow on the real preview, on desktop and phone sizes, and flags where the result doesn't match the intent: dead ends, confusing copy, layout breaks, errors.

3. 3

   You comment on the video

   Watch the walkthrough, click the spot that's wrong and say why. Walkproof works out which element you meant from the page's state at that moment, and where it lives in the code.

4. 4

   Fixes go back to the PR

   Press Send to post a review with screenshots and links to the exact second. Your coding agent gets the same items as a fix brief, and the next commit re-checks them.

Every walkthrough keeps the full picture

Everything is recorded on one clock, so any second of the video can be matched to exactly what the page was doing. That's how a click on the video becomes an element in your code.

Video

Desktop and phone, every step

Page structure

Rebuildable at any moment

Network

Every request, with failures

Console

Logs, errors and warnings

Storage and URL

Cookies, local storage, history

Accessibility

Names, roles, violations

Performance

Load, layout shift, responsiveness

Agent steps

What it tried and what it saw

Fits the workflow you already have

Safe to point at real work

Nothing posts without you

Walkproof drafts the review. It reaches the PR only when a person presses Send.

Isolated runs

Each walkthrough runs in a fresh, throwaway browser that can only visit your preview.

Masked by default

Typed form values and auth headers are kept out of recordings, and you can mask more.

Read-mostly access

The GitHub App can read code and post reviews. It never pushes code.

Questions

Does it replace our end-to-end tests?

No. Tests check what you already know to check. Walkproof looks at what a PR changes, from a user's point of view, and catches what nobody wrote a test for.

Which apps does it work with?

Any web app that gets a preview URL per pull request. Vercel comes first, then Netlify, Cloudflare Pages and any URL your own CI passes in.

Does it change our code?

No. It writes review comments and a fix brief. You, or your coding agent (Claude Code, Codex, Cursor), make the change, and Walkproof checks it on the next commit.

What about previews behind a login?

Walkproof uses your host's bypass token for automation and test accounts you provide. Both are stored encrypted and used only for your project's runs.