Skip to main content

Workspace Files

Workspace files give agents durable file-style storage for notes, scratchpads, logs, todos, task progress, generated code, and research files.
The workspace has two clear areas:
  • files/ — agent-managed files for scratchpads, todos, progress, preferences, notes, subagent outputs, and generated work.
  • artifacts/ — runtime-managed tool output artifacts created by tool offloading and read back with artifact tools.
There is no separate workspace-files backend: choose the workspace backend once, and both areas use that same local, S3, or R2 workspace.

Workspace Backends


Quick Setup

Workspace files default to local disk. Choose S3 or R2 only when the whole workspace should live in cloud storage.
With the local backend, workspace command tools write under:
For example, the prompt above creates ./workspace/files/notes/plan.md. Cloud workspace storage uses the S3/R2 extra:

Environment Variables

Local

S3

R2


Workspace Command Tools

OmniCoreAgent exposes these tools for the files/ area: These are workspace tools, not host shell tools. They operate through the active workspace backend, so the same tool calls work on local disk, S3, and R2. When workspace files are enabled, these tool names are reserved for the harness. Use distinct names for application-owned local tools.

Backend Behavior


Use Cases


Example: Research Agent with Cloud Workspace

Use local for development. Use s3 or r2 when the whole workspace should persist across server restarts, multiple agent instances, or production deployments.