Sandbox Agent workspace and artifacts (BETA)

Every sandbox has a workspace: the folder where files live during a turn. You can upload your own files for the agent to process, and the agent can publish a file as a downloadable artifact. This page is part of the Sandbox Agent BETA feature (overview).

Upload files into the workspace

From the conversation, you can upload files into the sandbox workspace. The agent then finds them via its file tools (read_file, filesystem) and can read, transform, or write new ones.

Uploads are quota-enforced: the total size of workspace files is capped. If you hit the quota, the UI tells you — delete or replace files, or trim what you send.

Reminder: the workspace is ephemeral. It lives with the sandbox (~10 minutes) and disappears when it expires. To keep a result, publish it as an artifact.

Publish an artifact

When the agent (or you, via its instructions) wants to hand you a result, it uses publish_artifact to turn a workspace file into a downloadable artifact. An artifact:

• is downloadable from the conversation;
• has an expiry: after it, the artifact is no longer available for download.

So grab important artifacts before they expire. For a deliverable you want to keep long-term, download it and store it on your side.

Good to know

• Uploaded files and artifacts are scoped to their sandbox context; nothing "leaks" to another agent or conversation.
• To keep an intermediate working state between steps within a single turn, the agent can also use checkpoints.

Next steps

• Agent tools — write_file, read_file, publish_artifact, checkpoint.
• Conversations and turns — the sandbox lifecycle.