Skip to main content

​
Creating a Checkpoint

Capture the current state of a running sandbox:
The checkpoint saves the filesystem and installed state. Status starts as processing and transitions to ready.

​
Forking from a Checkpoint

Create new sandboxes from a saved checkpoint. Each fork is independent:
Forked sandboxes start with a fresh boot from the saved disk state — don’t assume running processes carry over.

​
Restoring

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

​
Listing and Deleting

Each sandbox can have up to 10 full checkpoints and up to 100 disk-only checkpoints. To create a new checkpoint at the limit, opt into automatic deletion of the oldest eligible checkpoint of the same type:
Retention skips public checkpoints, patched checkpoints, and checkpoints that are still referenced by forked sandboxes.

​
Checkpoint vs Hibernate

Use checkpoints when you need to explore multiple paths from the same state. Use hibernation when you just want to pause and resume later.
SDK usage: Checkpoints. Full flags: CLI Reference.