Pause it. Come back exactly where it was.
Pausing keeps a sandbox’s memory and files. Resuming brings it back as it was, so an agent can stop for the night and carry on in the morning.
Pause and resume
Pausing keeps a sandbox’s memory and files. Resuming brings it back as it was, so an agent can stop for the night and carry on in the morning.
StepKept
Pausememory and files
Pausednothing runs, nothing counts against your hours
Resumeprocesses carry on where they stopped
- Kept
- Memory, open processes and files
- Billing
- Paused time doesn’t count against your hours
How it works
Three steps, the same from the API, the CLI or your agent over MCP.
01Pause
Memory is written out alongside the files, so nothing in flight is lost.
02Wait
A paused sandbox doesn’t use vCPU-hours.
03Resume
Memory is read back and the processes carry on.
Which plans
Pause and resume 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