Skip to main content
Proof is in beta, so some details on this page may still change.
Reading a diff tells you what changed. It doesn’t tell you whether the thing works. Proof does that part: it boots your app in its own sandbox, tries the change the way a person would, and posts screenshots or a recording back to the pull request. When a PR changes something that already exists, Proof runs the same scenario on the old code and on the PR, so you can see the difference instead of taking the description’s word for it.

What you get back

A UI change: the same clicks on the old code and on the PR.
A Proof comment with recordings of turning on dark mode before and after the change

Turn it on

Go to Settings → Proof and pick when it runs: Running on its own doesn’t mean running on every push. Proof runs when code that actually runs changes, and skips PRs that only touch tests, docs, CI or formatting. Want a different line? Write it down in Proof rules.

Ask for it yourself

Any of these runs Proof, in any mode. Rules only filter automatic runs.
  • Comment @codesmith prove it on the PR.
  • Click the Proof button in the PR description. It only shows up if your org has Edit PR descriptions turned on in [code]smith settings.
  • Ask [code]smith in a session, or use /proof <PR URL>.
  • Re-run the Proof check on GitHub, if your org shows Proof checks.
Want it to look at something specific? Say so: “prove it, and check the empty state on mobile.” Your notes add focus. They can’t talk Proof out of checking the main change.

What it costs

You pay for the compute and tokens Proof uses. No seats, no per-run fee. See Proof pricing.

Current limitations

Proof’s sandbox runs Linux, so it can’t run iOS, iPadOS, watchOS, visionOS or macOS apps yet. On those PRs it checks what does run on Linux, like the backend, and lists the rest in its report as claims to check on a Mac.