ade proof CLI. Captures are intentional — you run a command when a moment deserves evidence. Each capture is scoped to the chat or lane it runs in: agents launched inside ADE pick up the right owner automatically from the session they’re running in, so most captures need no owner flags at all.
Capture, then it’s filed
1
Capture or attach
Run
ade proof capture to screenshot the current state, or ade proof attach <path> to promote a file you already produced.2
ADE files it
The file is copied under
.ade/artifacts/computer-use/ and a row is written to the project database with its owner link.3
Review in ADE
The proof appears in the chat drawer and at lane / PR review, where you can accept it, request more, or dismiss it.
Command reference
ade proof capture — screenshot the current state
ade proof capture — screenshot the current state
Take a screenshot now and file it as proof for the current session.
The owner is inferred from the session you’re in. If no owner can be resolved and no flags are passed, the command exits non-zero — an un-owned proof has no home in the UI.
ade proof attach — promote an existing file
ade proof attach — promote an existing file
Promote an image, video, or browser-trace file you produced out-of-band — a headless-browser screenshot, a Playwright trace rendered as PNG, anything on disk.The proof kind is inferred from the file extension: images become screenshots,
.mov/.mp4/.webm become recordings, .zip/.har become browser traces. The original file is left in place; ADE copies it into .ade/artifacts/computer-use/.ade proof list — see what you've captured
ade proof list — see what you've captured
Print the proof set for the current session as JSON. Primarily for agents to see what they’ve already captured.
ade proof status — check capture capabilities
ade proof status — check capture capabilities
Report whether the runtime can capture (
screencapture availability, OS support).ade proof record --seconds <n> records a short video proof where supported.ade proof ingest — bring in evidence from another tool
ade proof ingest — bring in evidence from another tool
Ingest externally produced artifacts directly through the proof broker, with owners set in one call. Owner kinds are Each input needs real content through
chat (alias for chat_session), lane, pr (alias for github_pr), linear_issue, and automation_run.path, uri, text, or json. Paths must resolve inside an allowed import root (the project’s .ade/artifacts or .ade/tmp, the OS temp dir, or ~/.agent-browser).Run
ade help proof for the complete, current flag list. The ade proof commands print a JSON summary on success and exit non-zero on failure.Review proof
The capture, review, and attach lifecycle.
Proof configuration
Storage, retention, and troubleshooting.