Skip to main content
A checkpoint is a named snapshot of a running sandbox. Fork new sandboxes from it to start from a known-good environment — like git branches for VMs.

Checkpoint Types

OpenComputer supports two checkpoint modes: Full checkpoints are the default. Use kind: "disk_only" when creating autosaves or high-frequency checkpoints where disk state is enough.

Checkpoints vs Hibernation

What Gets Preserved

Checkpoints capture the filesystem and installed state. Forked sandboxes start with a fresh boot from that disk state — the platform attempts warm restore when possible, but may fall back to a cold boot. Don’t assume running processes carry over.

API Reference

Create Checkpoint

Checkpoint name must be unique within the sandbox. Status transitions from processing to ready (or failed). Each sandbox can have up to 10 full checkpoints and up to 100 disk-only checkpoints. To create a new checkpoint without failing at the limit, pass a retention policy that deletes the oldest eligible checkpoint of the same type first:
Retention skips checkpoints that are public, have patches, or are still referenced by forked sandboxes. If no eligible checkpoint of the requested type can be deleted, creation fails instead of deleting protected state.

List Checkpoints

Fork from Checkpoint

Creates a new sandbox from a checkpoint:

Restore Checkpoint

Revert a sandbox in-place. All changes since the checkpoint are lost:

Delete Checkpoint

CheckpointInfo

The TypeScript SDK returns typed CheckpointInfo objects. Python returns raw dictionaries with the HTTP API field names.

Example: Parallel Exploration

Try multiple approaches from the same starting point:
CLI equivalent: oc checkpoint. Full reference: TypeScript SDK · Python SDK · HTTP API.