The Agent Workspace

Files (Drive)

Browse, upload, and edit your Agent's persistent Drive — the working directory and knowledge base it reads and writes during every task.

Every Agent has its own Drive — a persistent file system that survives across sessions and sandbox restarts. The Files tab is a full browser into that Drive, so you can drop in reference material, watch the Agent's outputs appear, and edit anything by hand.

Files in the Agent workbench

What's in Drive

Drive is the Agent's working directory and knowledge base in one. It holds:

  • Documents you upload as reference material
  • Files the Agent generates during tasks
  • Code, configs, and data it works with
  • Outputs from terminal commands and browser automation

Files persist — the Agent can reach them at any time without re-uploading, and they're mounted into the cloud computer so the Terminal and Git tabs see the same tree.

Browse and edit

The Files tab shows a folder tree on the left and a preview on the right.

  • Click a folder to expand it; use the breadcrumb to navigate back up
  • Click a file to preview it; double-click to open the inline editor
  • Edits save automatically — the Agent sees the new content the next time it reads the file
  • Right-click a file or folder for rename, move, share, and delete

Deletion is permanent — there is no trash.

Upload, create, and share

  • Upload — drag files into the tab or use the Upload button; large files are chunked automatically with inline progress
  • New file / folder — create from the toolbar; new items are immediately available to the Agent
  • Share — generate a time-limited share link for any file from its right-click menu

How the Agent uses Drive

The Agent's working directory is rooted in its Drive, so anything it writes with a command or code execution lands here automatically. You can point it at files in plain language:

Summarize the file at /reports/q1-2024.pdf

The Agent locates and reads the file with no extra setup.

Storage type

When you create an Agent you choose its storage tier. Code-heavy work (installs, builds, Git) is much faster on a high-performance volume — see High-performance volume.

On this page