Docs

Proofsheet docs

Proofsheet has two parts. The hub runs on the Mac your phones plug into, and your coding agent drives the phones through it. The portal at proofsheet.dev keeps every run your team uploads and shows it to the people you choose.

• QuickstartInstall the hub and get a first run on an Android phone.
• iPhone setupXcode, your Apple team, and the one command that builds for your iPhones.
• Writing flowsTests as numbered steps in plain language, recorded once, replayed on any phone.
• Sharing with clientsInvite a client to their projects, publish runs, choose what they see.
• Plans and storageFree and Pro, what counts as storage, upgrading and cancelling.
• TroubleshootingWhat each proofsheet doctor line means and how to fix it.

How the parts fit

• The hub is the proofsheet command and Proofsheet.app, which keeps it running. It finds the phones plugged into the Mac by USB and hands each one to one run or agent at a time.
• Your agent (Claude Code, Codex or Antigravity) talks to the hub through the proofsheet MCP server and follows the proofsheet skill, which proofsheet init adds to your repo.
• Flows live in your repo, in e2e/proofsheet/flows/. Each run is written on the Mac and uploads to your workspace when it finishes.
• Your workspace lives at yourteam.proofsheet.dev: its runs, flows, comments, members and clients.

What you need

• A Mac with Apple Silicon on macOS 26 or later, with the phones plugged in by USB.
• A coding agent: Claude Code, Codex or Antigravity.
• Node.js, for npx: proofsheet init uses it to add the skill to your repo.
• For Android phones: adb. For iPhones: Xcode and an Apple developer team (iPhone setup).

Web flows are coming. Today Proofsheet runs flows on iPhone and Android phones and tablets.