Proof setup and CLI

On macOS, ADE uses built-in tools for screenshots and short recordings. The first capture may require Screen Recording permission in System Settings -> Privacy & Security.

Common commands

Command	Use
`ade proof status --text`	Check available capture capabilities.
`ade proof list --text`	List proof artifacts for the current scope.
`ade proof screenshot`	Capture a screenshot.
`ade proof record --seconds 20`	Capture a short recording.
`ade proof ingest --input-json '{...}'`	Ingest a trace, log, or verification from another tool.

Typical flow

Capture evidence

Run a screenshot, recording, or ingest command from the relevant lane/session.

Store locally

ADE writes the file under .ade/artifacts/computer-use/ and records metadata in the local database.

Attach owners

Link the proof to a chat, lane, PR, Linear issue, or worker activity.

Review in ADE

Open the proof from the UI and accept, request more, or dismiss it.

Ingest external evidence

Use ade proof ingest for output from browser tests or other verification tools:

ade proof ingest --input-json '{
  "backend": { "name": "playwright" },
  "inputs": [
    { "kind": "browser_trace", "title": "checkout flow", "path": "/tmp/trace.zip" },
    { "kind": "console_logs", "title": "checkout console", "text": "..." }
  ],
  "owners": [
    { "kind": "pull_request", "id": "123" }
  ]
}'

If screenshots are blank, restart ADE after granting Screen Recording permission.

Proof workflowCapture, review, and attach evidence to chats, lanes, PRs, Linear issues, and worker activity.

Settings Reference

Project Configuration

Computer Use

AI Tool Integrations

Proof setup and CLI

Common commands

Typical flow

Ingest external evidence

​Common commands

​Typical flow

​Ingest external evidence

Common commands

Typical flow

Ingest external evidence