Fork Sandbox
Checkpoints a running source sandbox and creates an isolated writable disk branch. Forks from running or paused sources resume from the source’s CPU, memory, and disk state. Forks from stopped sources cold-boot from the saved disk checkpoint. A running source is resumed after its checkpoint; paused and stopped sources remain inactive. Forked sandboxes may themselves be forked.
Passing checkpoint forks that saved state without touching the
source, so clients can pause once, wait for the checkpoint, and fork
it from any number of places. Without checkpoint the server pauses a
running source inside the request and resumes it afterwards; that path
is kept for older clients and is bounded by the request timeout.
Authorizations
API key
Path Parameters
Sandbox UUID
Query Parameters
Hold the request for a completed sandbox lifecycle transition
Body
Name for the fork. A random word-list name is generated when omitted.
1 - 63^[a-z0-9]([-a-z0-9]*[a-z0-9])?$Fork this checkpoint of the source, as returned by pause, stop, or describe, instead of the source's live state. The source is neither paused nor resumed. Only the current session's checkpoint and the one before it are accepted; an uncommitted or superseded checkpoint is rejected with 409.