> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-dependabot-github-actions-actions-cache-6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Proof

> Capture screenshots, recordings, browser traces, console logs, and verification notes as evidence for agent work — linked to the chat, lane, PR, or Linear issue they belong to.

**Proof** in ADE is *intentional* evidence — a screenshot, recording, browser trace, console log, or verification note — captured at the moment a result is visible to show that a change actually does what it claims. Agents often say they tested something; proof makes that claim inspectable, and ties it to the work it belongs to.

Nothing watches your agent and files screenshots for it. When the agent (or you) reaches a checkpoint worth showing — a login succeeds, a form submits, an error reproduces, a test passes — proof is captured on purpose and normalized into one canonical artifact model that a reviewer can skim in under a minute.

<CardGroup cols={3}>
  <Card title="Evidence, not chatter" icon="camera">
    Concrete artifacts a reviewer can open, instead of a claim buried in a transcript.
  </Card>

  <Card title="Tied to the work" icon="link">
    Every proof links to a chat, lane, PR, or Linear issue — and can link to several at once.
  </Card>

  <Card title="Intentional capture" icon="hand-pointer">
    Captures are deliberate. There's no auto-observer; the agent or you decide a moment deserves evidence.
  </Card>
</CardGroup>

## Proof kinds

ADE normalizes every capture into one of five canonical kinds, whatever tool produced it.

| Kind                  | Use it for                                               |
| --------------------- | -------------------------------------------------------- |
| **Screenshot**        | Show the visible state of an app or browser.             |
| **Recording**         | Capture a short interaction or repro.                    |
| **Browser trace**     | Preserve browser steps and diagnostics from a test tool. |
| **Console logs**      | Attach useful runtime or browser output.                 |
| **Verification note** | Record what was checked and why it passed.               |

<Frame caption="Capture exactly what the agent sees — the same view a reviewer needs.">
  <img src="https://mintcdn.com/ade-ac1c6011-dependabot-github-actions-actions-cache-6/mZiHD0-x8whDsXL3/media/features/browser/browser-inspect.webp?fit=max&auto=format&n=mZiHD0-x8whDsXL3&q=85&s=5a01fd61dbbc4854701c227c7a151709" alt="Inspecting a page in ADE's browser pane" width="1280" height="658" data-path="media/features/browser/browser-inspect.webp" />
</Frame>

## What proof attaches to

Every artifact carries at least one owner. A single artifact can link to more than one, so it surfaces wherever the work is reviewed — and evidence can flow from an exploratory chat to a PR comment without losing provenance.

* **Chat** — the proof drawer below the composer in the session that produced it.
* **Lane** — alongside the worktree's diff and review.
* **PR** — surfaced at pull request closeout, where reviewers look.
* **Linear issue** — attached to the issue when Linear is connected.
* **Automation run** — captured as part of a dispatched agent or worker run.

## Where it fits

<Steps>
  <Step title="An agent reaches a checkpoint">
    A UI change renders, a flow completes, a test passes, an error reproduces.
  </Step>

  <Step title="Proof is captured">
    The agent or you capture a screenshot, recording, trace, log, or note with a short caption.
  </Step>

  <Step title="A reviewer sees it">
    The artifact rides along with the chat, lane, PR, or issue — so the result is verifiable, not just asserted.
  </Step>
</Steps>

<Tip>
  Capture proof at the moment the result is visible, and write captions like a teammate is reading them. A good proof set is three to eight captures with captions a reviewer can read in one pass — not a screenshot after every click.
</Tip>

<CardGroup cols={2}>
  <Card title="Capture proof" icon="terminal" href="/computer-use/setup">
    Prerequisites and the `ade proof` capture commands.
  </Card>

  <Card title="Review proof" icon="camera" href="/computer-use/proofs">
    The capture, review, and attach lifecycle in detail.
  </Card>
</CardGroup>