Stop sandbox
Stop active work and archive/snapshot the sandbox for later resume or fork.
A stop always saves the sandbox’s disk first. If that save is failing, the stop is refused and the sandbox keeps running so your work is not discarded, we retry automatically and email you. You are not billed for time spent in that state.
The stop is an operation: the response and the sandbox carry it as stop, with an
id and a status. Poll GET /sandboxes/{sandboxId} until stop.status is
completed. A failed attempt shows failing with its error and is retried
until the sandbox archives; commands and prompts you send meanwhile do not cancel
it. Only a resume ends it early (superseded). Calling stop again while one is
pending returns the same id.
Set force: true to stop anyway, keeping the last successful snapshot and
losing everything written since then. This is irreversible; only reach for it
after a stop has already failed. A force on a stop that is already pending
escalates that stop.
Authorizations
Boat bearer token in the form boat_.... Service API keys authenticate sandbox operations.
Path Parameters
Public Sandbox id returned by create/list/get sandbox calls.
^bx_[23456789abcdefghjkmnpqrstuvwxyz]{8}$Body
Options for stopping a sandbox.
Stop the sandbox even if its disk cannot be snapshotted. It keeps its last successful snapshot and everything written since then is permanently LOST. Without this, a sandbox whose snapshot pipeline is failing is left running rather than discarding your work, and you are not billed for that time. Only use this after a stop has already been refused.
Response
Boat archival started or already in progress.
true
Stable success envelope discriminator added by v1.
"sandbox.stopping"
"archiving"
Present on resume or fork when a fair-use cap on a gifted account shortened the requested auto-stop time.
On interrupt, the conversation whose turn was interrupted.