> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cotool.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Filesystem

> Keep an agent's files and workspace between runs

By default, an agent starts each run from a clean slate. **Agent Filesystem** changes that: when it's enabled, the agent's workspace **persists between runs**, so files, notes, and tool state carry forward instead of resetting every time.

<Note>
  Agent Filesystem is in **Beta**.
</Note>

## Viewing Files

The files in an agent's workspace are viewable directly in the UI, where you can browse the workspace, preview files, and download them.

## Persisting Files Across Runs

Turning on **Agent Filesystem** keeps an agent's workspace between runs. This is useful when an agent should:

* Build on prior work instead of starting over each run
* Reuse reference files, lookup tables, or templates you upload once
* Keep packages or scripts it installed available for later runs

### Enabling It

<Steps>
  <Step title="Open the agent">
    Go to **Agents** and open the agent you want to update.
  </Step>

  <Step title="Turn on Agent Filesystem">
    Find the **Agent Filesystem** card and flip the toggle to **On**.

    On the agents and detections list pages, you can also use **Learn more** on the Agent Filesystem banner to enable it for several agents at once.
  </Step>

  <Step title="Manage the files">
    Once enabled, the agent gets a persistent workspace panel where you can browse, upload, download, and delete files.
  </Step>
</Steps>

### Managing the Persistent Workspace

From the workspace panel you can:

* **Upload** files with the Upload button or by dragging them onto the panel
* **Download** any file, or a whole folder as a zip
* **Delete** files and folders you no longer need
* **Preview** text, markdown, and image files without downloading

Files you upload and files the agent creates share the same workspace, so the agent can pick up where it left off.

<Note>
  Use the persistent workspace for files that should stick around, like reference data or reusable scripts. Keep large, run-specific scratch output (such as raw logs) out of it so the workspace stays tidy.
</Note>

## Agent Filesystem vs File Attachments

These are related but separate:

| Use this for...                           | Agent Filesystem   | File Attachments |
| ----------------------------------------- | ------------------ | ---------------- |
| Files the agent creates during a run      | Yes                | No               |
| Files that carry across runs              | Yes (when enabled) | No               |
| Files you upload to a single chat message | No                 | Yes              |

See [File Attachments](/chat/file-attachments) for uploading files directly to a chat message.