Where do sandbox deliverables go?

The writable workspace is backed by a directory on your computer. Task containers can be removed after execution while deliverables remain in that local workspace.

Before you begin

A workspace determines where a teammate executes work and saves files. The environment is captured with a task, so changing a teammate later does not rewrite an earlier task. Local execution and Docker isolation have different permissions; read the selected mode before submitting real project data.

Steps

1. Open the finished task and Results.
2. Inspect the recorded deliverable paths.
3. Open the teammate workspace if a file is missing from the list.

Example

Ask for /workspace/outputs/summary.md rather than saving work to a temporary container directory that may disappear with cleanup.

Check the result

Open the physical file after the task has ended and verify that its content matches the requested deliverable.

Limits and troubleshooting

Files written outside mounted persistent paths may not survive container cleanup. A message claiming completion is not a saved artifact.