Evidence keeps the observation behind a finding with the review. It can be attached to a specific comment or added to the review as a general item.

## Inspect evidence in Desktop

Open the **Evidence** tab to see evidence from the whole review. The tab groups attachments by their source comment and lets you:

- filter by image, video, text, or link;
- open an item at a larger size;
- jump back to the source comment and code location.

Evidence attached to a finding also appears with that finding, so you do not have to leave the code view for every item.

## Add evidence in Desktop

In the **Evidence** tab, use the add button or drop files onto the tab. You can also paste an image or file while the tab is open. EV adds these as general review evidence.

To keep evidence with a specific observation, add or reply to a comment and attach the item there instead.

## Let a reviewer skill gather evidence

Reviewer skills can be allowed to operate a browser and attach artifacts to the active review. This is useful when a visual check is part of the review itself: the reviewer can inspect the running interface, capture the relevant state, and store the screenshot alongside its findings.

For example, the EV repository provides a project-local `screenshot-evidence` skill for work on EV Desktop. It connects to a debug build, captures the home screen and a populated review, and immediately adds both images as agent-authored evidence.

Check whether a project provides the skill:

```sh
ev skills list
ev skills show screenshot-evidence
```

Then include it in a review:

```sh
ev review -b origin/main --desktop --skill screenshot-evidence
```

The skill requires EV Desktop to be running with its documented debug port. It stops with that setup instruction if the app is not reachable; it does not silently substitute an unrelated screen capture.

`screenshot-evidence` is a repository-specific example rather than a built-in skill. See [Use reviewer skills](/docs/guides/reviewer-skills/) for where EV discovers project and user skills and how evidence permissions work.

## Add image evidence from the CLI

Agents and scripts can attach an image to a review:

```sh
ev evidence add \
  --review rev-abc \
  --image ./artifacts/home.png \
  --title "Home screen after sign-in" \
  --description "The empty state remains visible after the project loads"
```

`--review` may be omitted when EV supplies `EV_REVIEW_ID` to the review agent. The image and title are required; the description is optional.

## Attach evidence to a comment

`ev comment add --attach` accepts a local image or video, a URL, or a `text:` note. Repeat the option to attach more than one item:

```sh
ev comment add \
  --review rev-abc \
  --file src/home.tsx \
  --line 42 \
  --content "The loading state never clears" \
  --attach ./artifacts/loading.png \
  --attach "text:Reproduced after a fresh launch"
```

Use a comment attachment when the evidence supports a particular finding or code location. Use general evidence when it describes the review as a whole.