Files and durable work
Use these guides when an Agent needs durable mutable files or must deliver a file to your application. Choose the workflow based on whether the file should remain private workspace state or become a tenant-accessible Artifact.
Choose a guide
Configure file operations
Attach a durable Sandbox and prove that one file persists across Turns.
Build a coding Agent
Enable the read, write, edit, search, and command Tools for a bounded workspace task.
Publish and download Artifacts
Publish selected workspace files, then list and download their immutable bytes.
Understand the storage boundary
A Sandbox holds private, mutable workspace files for its attached Agent. Those files persist across Sessions and Turns, but your application cannot list or download the workspace through the public API.
An Artifact is a file the Agent deliberately publishes from that workspace. Artifacts are immutable tenant resources that your authenticated backend can list and download. Enabling file operations does not publish scratch files automatically.
Prerequisites
- An existing Agent
- A backend TypeScript SDK client
- An understanding of Sandboxes and file operations
- The broader Guides index when your workflow also needs integration, extension, or automation guidance