Skip to main content
POST /v1/agents/runtime/{runtime_id}/fork · POST /v1/agents/snapshots/{snapshot}/fork Fork captures the parent’s state once, then starts every child from that capture. The parent keeps running with its own ID. Each child is an ordinary sandbox — its own ID, timeout, and filesystem. Results are per-child: one failure never fails the request. Inspect every entry in children.

Parameters

Response

Notes

  • The parent must be running. A paused parent returns 409 runtime must be running to fork — resume and retry.
  • Children inherit the parent’s environment variables; per-session credentials are regenerated on each child.
  • A child that shows status: "running" may take a moment before commands and file operations respond — retry briefly on a fresh child.
  • A forked child is fully independent: writes on one child never appear on the parent or siblings.
  • With persist_snapshot: false (default) the capture is removed once every child has started; it does not appear in your snapshot list.