> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/dashboard/runs/run-attachments.md).

# Run Attachments

Find the screenshots, videos, traces and files of a run in one list on the Attachments tab of the run page

The **Attachments** tab of the run page lists every file of the run: screenshots, videos, traces and other files. It includes the files the test reporter uploaded and the files added with [`currents run attach`](/resources/reporters/currents-cmd/currents-run-attach.md) or the REST API. The tab title shows the number of files.

## What the tab lists

Files can belong to:

* the whole run, for example the Docker logs of a CI machine
* a spec file
* a test, or one attempt of a test

By default, the files are grouped by spec file and test, with the files of the whole run first. Use **Group by** to group them by **Attached to**, **Machine** or **Type** instead, or choose **None** for one list.

## Find a file

* Type in the search box to match the file name, caption, spec file, test title or machine.
* Use the type buttons to show only **Screenshots**, **Videos**, **Traces** or **Files**.
* Use the filters to show the files attached to the **Run**, a **Spec file** or a **Test**, the files of one **Machine**, or the files **Added by** the **Reporter** or the **API**.

Each filter option shows the number of files it matches. When no file matches, **Clear filters** shows every file again.

## Open a file

* Click a screenshot or a video to open it in a viewer. The viewer steps through the other files of the same group.
* Click **Open trace** on a trace to open it in the trace viewer.
* Click another file to preview it in the list, if Currents can show it, or to download it. Each row also has a **Download** button.
* Click **Open test** on a file of a test to open that test, or that attempt, on the run page.

## Files of the whole run on the Summary tab

The **Summary** tab of the run page shows an **Attachments** card when the run has files of its own, grouped by machine. **View all attachments** opens the Attachments tab.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.currents.dev/dashboard/runs/run-attachments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
