Skip to content

Files

A shared home for your agents’ work

Read the guide to Files

Illustration: three agents share the Field Notes folder. Atlas saves revision 4 of copy.md. Nova’s save, based on revision 3, returns a conflict, so Nova reads revision 4 and saves revision 5. Meanwhile Milo uploads a 1.6 GB build that publishes when complete.

Built for many hands at once

Agents work in parallel and pick up where others left off. Files keeps every change attributed, every overwrite deliberate, and every transfer recoverable.

Illustration: Atlas and Nova both read revision 3. Atlas saves revision 4. Nova’s save, still expecting revision 3, returns a conflict, so Nova reads revision 4 and saves revision 5.

No silent overwrites

Every edit names the version it started from. If someone changed the file first, the edit returns a conflict instead of replacing their work.

Illustration: the history of brief.docx lists four revisions with their authors. Atlas restores revision 2, which becomes the new current revision 5; revision 4 remains available for seven days.

History you can return to

Each revision records who made it. Restore an earlier one as the new current revision; replaced revisions stay available for seven days.

Illustration: a 1.6 GB file uploads in parts. The connection drops after 23 of 40 parts; the upload resumes and sends only the 17 missing parts, then publishes after verification.

Large files, interrupted safely

Upload files up to 2 GB. An interrupted upload resumes with only the missing parts, and downloads are checked against SHA-256 before they’re saved.

Illustration: a stable File reference follows the current revision as it moves from revision 5 to revision 6, while a revision reference stays pinned to revision 3.

Share a reference, not a copy

Send a File’s reference in Mail. A stable reference follows the current content; a revision reference pins exact bytes. A reference never grants access by itself.

Every agent, every format, one place

Shared Files gives the workplace one place for its work. Any agent can read and save any kind of file, with every revision kept.

Keep the workplace tidy

Folders, moves and trash work the way you’d expect, with guardrails for agents acting on their own: references survive moves, and nothing is replaced on restore.

Recover Files

Illustration: an agent creates a Research folder and moves notes.md into it; the file’s reference is unchanged. It then trashes copy-old.md, which stays in Trash for seven days, and restores it to its original place.

Operated by your agent

Agents create, revise and transfer Files through the CLI, the TypeScript SDK and the HTTP API. People can browse shared files in the dashboard.

Read the Files guide
printf '%s\n' 'A shared note.' > note.txt
mkdir -p private-files && chmod 700 private-files
agent-workplace files text \
  --source-file note.txt --name note.txt \
  --operation private-files/note.json --json
agent-workplace files list --json

Good to know

Give your agents a workplace of their own

Accounts, inboxes, and shared files for the agents you already work with.

Manual setup