# Files and memory

Sandboxes are temporary. Anything that should outlive a task is saved as a file or as memory.

A **file** is a durable, versioned artifact in the project, such as a report the agent wrote. **Memory** is a set of files private to one owner that later tasks for that owner see again.

**You need:** `introspection login` and a task that wrote files.

## Know where to write

| Folder | Holds | Survives |
| --- | --- | --- |
| `/workspace/files` | Attached uploads and the recipe's `files/` (read-only); files the agent adds | Uploads unchanged; added files are saved like outputs |
| `/workspace/outputs` | Deliverables | The task, including a replaced sandbox |
| `/workspace/memories` | The owner's memory | Later tasks for the same owner and environment |
| Anywhere else | Scratch work | Lost with the sandbox |

Outputs and memory are saved after each turn and when the task ends; sizes are in [Limits](/reference/limits). To set memory up, see [Memory and deleting data](/patterns/memory-and-data).

## Find a task's files

```bash
introspection files list --filter task_id=<task-id> --filter category=output
introspection files content <file-id> --out report.md
```

In the dashboard: **More → Files**. Filters (`--filter KEY=VALUE`, repeatable):

| Key | Values |
| --- | --- |
| `task_id`, `conversation_id` | One task's files |
| `category` | `output`, `memory`, or `file` |
| `file_type` | `upload`, `filesystem`, `other` |
| `name`, `name_contains`, `storage_path` | Name match |
| `content_format`, `versioned` | Format, or whether it has history |
| `tag`, `metadata` | `key:value` |

## See older versions

Each write creates a version:

```bash
introspection files versions list <file-id>
```

There is no restore command. Reading an older version's content needs object-store versioning on the data plane; otherwise `files content` returns the current bytes for any version id.

Concurrent tasks for one owner can start from the same memory and overwrite
each other. Run tasks that write the same owner's memory one at a time.

## Limits

| Not supported | Do this instead |
| --- | --- |
| Some filters (such as `category`) in the JS SDK's `files.list` | Use the CLI or the REST API. |
| Storing secrets in files or memory | Use [credentials](/ship/bindings). |
| Shared memory across owners | Share a file by tag ([Sharing](/identity/sharing)) and attach it to each task. |

Or ask your agent: "List the files task `<task-id>` produced and download the report."

Files and memory

Sandboxes are temporary. Anything that should outlive a task is saved as a file or as memory.

A file is a durable, versioned artifact in the project, such as a report the agent wrote. Memory is a set of files private to one owner that later tasks for that owner see again.

You need: introspection login and a task that wrote files.

Know where to write

Folder	Holds	Survives
`/workspace/files`	Attached uploads and the recipe’s `files/` (read-only); files the agent adds	Uploads unchanged; added files are saved like outputs
`/workspace/outputs`	Deliverables	The task, including a replaced sandbox
`/workspace/memories`	The owner’s memory	Later tasks for the same owner and environment
Anywhere else	Scratch work	Lost with the sandbox

Outputs and memory are saved after each turn and when the task ends; sizes are in Limits. To set memory up, see Memory and deleting data.

Find a task’s files


introspection files list --filter task_id=<task-id> --filter category=output
introspection files content <file-id> --out report.md

In the dashboard: More → Files. Filters (--filter KEY=VALUE, repeatable):

Key	Values
`task_id`, `conversation_id`	One task’s files
`category`	`output`, `memory`, or `file`
`file_type`	`upload`, `filesystem`, `other`
`name`, `name_contains`, `storage_path`	Name match
`content_format`, `versioned`	Format, or whether it has history
`tag`, `metadata`	`key:value`

See older versions

Each write creates a version:


introspection files versions list <file-id>

There is no restore command. Reading an older version’s content needs object-store versioning on the data plane; otherwise files content returns the current bytes for any version id.

Concurrent tasks for one owner can start from the same memory and overwrite each other. Run tasks that write the same owner’s memory one at a time.

Limits

Not supported	Do this instead
Some filters (such as `category`) in the JS SDK’s `files.list`	Use the CLI or the REST API.
Storing secrets in files or memory	Use credentials.
Shared memory across owners	Share a file by tag (Sharing) and attach it to each task.

Or ask your agent: “List the files task <task-id> produced and download the report.”