Copy the repo in. Copy the results out.

Move a source tree into a sandbox and pull reports, builds and logs back out, up to 1 GiB per file.

Sandboxes › Files in and out

Files in and out

Move a source tree into a sandbox and pull reports, builds and logs back out, up to 1 GiB per file.

Terminalsbx_9a20
01$ sandscale cp ./repo.tar.gz sbx_9a20:/workspace/
02repo.tar.gz → sbx_9a20 · 214 MB · done
03$ sandscale exec sbx_9a20 -- make report
04$ sandscale cp sbx_9a20:/workspace/report.html .
05report.html ← sbx_9a20 · done
Largest file
1 GiB
Where
/workspace in every template
Ways in
API, sandscale CLI, MCP read and write tools
Audit
Copies are recorded with their size

How it works

Three steps, the same from the API, the CLI or your agent over MCP.

01In

Copy a file or archive into /workspace from the CLI, the API or MCP.

02Work

Your agent builds and tests against exactly that tree.

03Out

Copy results back before you throw the sandbox away.

Which plans

Files in and out work on every plan.

See pricing →

Give every agent
a box of its own

Start free with 100 vCPU-hours a month. Upgrade when your agents need more.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI