Skip to main content
You can provide files to your agent by uploading them through the Files API and mounting them in the session’s sandbox.
Managed Agents API requests require the managed-agents-2026-04-01 beta header, except memory store endpoints, which use agent-memory-2026-07-22 instead. The SDK sets the correct beta header automatically. See Beta headers.

Uploading files

First, upload a file using the Files API:

Mounting files in a session

Mount uploaded files into the sandbox by adding them to the resources array when creating a session:
The mount_path is optional, but make sure the uploaded file has a descriptive name so the agent can identify it.
With the preceding mount_path, the agent reads the file at /mnt/session/uploads/data.csv (see File paths). A new file_id is created that references the instance of the file in the session. These copies do not count against your storage limits.

Multiple files

Mount multiple files by adding entries to the resources array:
A maximum of 500 files is supported per session.

Managing files on a running session

You can add or remove files from a session after creation using the session resources API. Each resource has an id returned when it is added (or listed), which you use for deletes.
List all resources on a session with resources.list. To remove a file, call resources.delete with the resource ID:

Listing and downloading session files

Use the Files API to list files scoped to a session and download them.

Supported file types

The agent can work with any file type, including:
  • Source code (.py, .js, .ts, .go, .rs, and others)
  • Data files (.csv, .json, .xml, .yaml)
  • Documents (.txt, .md)
  • Archives (.zip, .tar.gz) - the agent can extract these using bash
  • Binary files - the agent can process these with appropriate tools

File paths

Files mounted in the sandbox are read-only copies. The agent can read them but cannot modify the original uploaded file. To work with modified versions, the agent writes to new paths within the sandbox.
  • The path you specify is rooted under the session’s uploads directory: a mount_path of /data.csv places the file at /mnt/session/uploads/data.csv in the sandbox
  • If you omit mount_path, the file is placed at /mnt/session/uploads/<file_id>
  • Parent directories are created automatically
  • Paths should be absolute (starting with /)