Skip to main content
A File Store is a folder tree that belongs to one agent. Keep the reports it writes, the documents people upload and the files a coworker works on. You build any folder structure you like, and every change keeps a version. Add one with Add → File Store under an agent, and give it a name such as “Inbox” or “Reports”. It opens as an empty folder.

Work in a store

On the store’s page you can upload, make a new folder, rename, move, download and delete. Expand the store in the sidebar to see its top-level folders.
  • Move works inside a store, and between stores of the same agent.
  • Versions keep the last 3 versions of a file, and checkpoints you make. Open a file’s history to restore one.
  • Delete moves a file or folder to the Trash, where it stays for 30 days and can be restored.
  • Names match whatever their case.
  • All your stores and databases count toward your workspace’s 20 GB of storage.
Paths start at the store: reports/2026/q3.csv. The same files engine runs behind Workspace files, so everything you know about editing and history applies.

Use a store in a workflow

Four places take a File Store: Paths are then relative to the store. Leave the choice empty and the step uses Workspace files as before, labelled Workspace files (legacy).

Use a store with a coworker

Each File Store of a coworker’s agent shows up in its session as a folder at /workspace/files/<key>/. The coworker reads and writes there like any folder, and what it saves comes back as a new version. In text and instructions, write the path as files/<key>/<path>. Name a file in a message or a session’s opening text with @files/<key>/<path>. @files/<key> on its own names the store’s root:
Type @ in the message box and pick the file; the box inserts the mention for you. The old form @<key>/<path> is no longer read. The Task panel’s files/ list shows the agent’s File Stores as folders. The key of a store is its folder name. When you change it, @files/<key>/ and files/<key>/ are updated in the agent’s items. If something on a coworker’s computer is in the way of a store’s folder, it is moved to files-before-sync/<name> in the Task’s files, and you see a line about it in the transcript. Whatever cannot be moved stays only on the coworker’s computer and is not synced. You are told about that too. Until your workspace’s files have moved into File Stores (see below), your team’s Workspace files are also at /workspace/files, with the stores inside them as folders. A Workspace files folder with the same name as a store is hidden while the store uses that name. After the move, files/ holds only File Stores. A mention whose first folder is not a File Store of the agent names no file, and the message box warns you, for example: “files/Reports is not one of this agent’s File Stores, so the coworker will not find it.” See Data stores for coworkers.

Share a File Store

A store can be shared with the workspace’s other agents, your own app or an AI assistant from its Manage access: Read lets them list, download and search, and Read & write also lets them upload, make folders, move and delete. A coworker of another agent sees a store shared to read only as a read-only folder. Files never move or copy between your agent’s stores and another agent’s. See Use a store another agent shares and Agent data API.

In each environment

When the agent has more than one environment, such as Production and Demo, a File Store is one of two kinds:
  • Separate in each environment: each environment has its own files. Work in Demo never touches Production’s files. Every new File Store is separate.
  • The same in every environment: one set of files that every environment reads and changes.
Workflows, coworkers, the API and AI assistants use the files of the environment the agent runs in. A store another agent shares with yours always reaches that agent’s Production files.

The store’s page

A separate store’s page has a pill for each environment at the top, with its size. It opens on Production and marks the one the agent runs in. The line under the pills says whose files you see: “Showing Demo’s files. The agent runs in Production.” Upload, new folders, moves and deletes act on the environment you picked. A store that is the same in every environment says The same in every environment instead: “Every environment reads and changes these files.” When you add an environment, you pick for each separate store whether its files there start empty or as a copy of another environment’s. See Add an environment. A copy runs in the background, and the page says how it is going in place of the files: Until Demo’s files are ready, the agent can’t switch to Demo, and work in Demo that uses the store is refused: “Brochures has no files in Demo yet.”

Change it

Click Files per environment, beside the pills or the shared line. The change works only while the agent is stopped or runs in Production (“Stop the agent or switch it to Production first.”), and while no work outside Production is still in progress.
  • To separate (Give each environment its own files): Production keeps its files. Each other environment starts Empty or with a Copy of Production, and the dialog says the space the copies need.
  • To the same (Use one set of files): Production keeps its files. Each other environment’s own files go to the Trash, where they stay 30 days. The dialog lists them first, such as “Demo: 14 files, 2.1 MB”.
Each environment’s own files count toward your workspace’s storage. A copy that would take it above 80% of its limit is refused.

Your existing Workspace files

Workspace files, the one folder every agent shared, move into File Stores once, when File Stores arrive in your workspace:
  • Files labelled with an agent go into a File Store named Files in that agent, in the same folders.
  • Everything else goes into a File Store named Workspace files in Unsorted. Move it into agents whenever you like.
  • Steps, file triggers, Read File, Execute Code and coworker instructions are pointed at the store that now holds their files. Paths inside a store stay the same: @files/reports/q1.csv becomes @files/Files/reports/q1.csv.
  • An item that used a file now in another agent’s store is marked Needs attention. Move the file or the item so they share an agent, or dismiss the note.
  • Workflows with a file trigger keep running and watch the new store.
Files keep their versions and history through the move.

Sharing and installing

A shared copy carries every File Store, and with Include contents its files, from the environment you share from. The share screen shows the file count and size of each in that environment. The copy has only Production, and those files become its Production files. If copying the files fails, the store is still created, and Finish installation lists Files not copied with a Retry button. See Sharing agents.

Delete a store

Deleting a File Store moves its files to the Trash for 30 days, in every environment. The window shows what uses the store first.

Next steps

File Store step

Write, move, copy and delete files from a workflow.

Editing and history

Versions, checkpoints and the Trash.

Data stores

Variable groups and Databases too.

Agent data API

Offer a store to your app or an AI assistant.