filesystem: captures filesystem state and restores with a cold boot.memory: captures filesystem, memory, and running process state and restores with a warm start.
filesystem by default.
Snapshots are independent of sandbox lifecycle — once captured, the artifact persists after the source sandbox is terminated. This means you can snapshot an ephemeral sandbox before it ends, then restore that state into a new sandbox much later. If you only need to pause a single sandbox in place rather than produce a reusable artifact, use suspend/resume instead.
Creating a Snapshot
- CLI
- Python
- TypeScript
- HTTP
Restoring from a Snapshot
Create a new sandbox from a snapshot. If the snapshot is filesystem (default), the new sandbox restores the captured filesystem. You can change sandbox resources (CPU, memory, disk) for the new sandbox. If the snapshot is memory, the new sandbox restores filesystem, memory, and running processes exactly as they were. Image, resources (CPUs, memory), and entrypoint come from the snapshot and cannot be changed at restore time. If you need different resources, create a fresh sandbox instead of restoring. For filesystem snapshots, you can pass--disk_mb / resources.disk_mb at restore time to grow root disk size (growth-only).
- CLI
- Python
- TypeScript
- HTTP
Clone a Sandbox
tl sbx clone creates a memory checkpoint and immediately boots a new sandbox from it, so the clone warm-restores filesystem, memory, and running processes from the source. The intermediate snapshot persists — it shows up in tl sbx checkpoint ls and counts toward storage until you delete it with tl sbx checkpoint rm <snapshot-id>.
- CLI
- Python
- TypeScript
- HTTP
Managing Snapshots
List Snapshots
- CLI
- Python
- TypeScript
- HTTP
Get Snapshot Details
- TypeScript
- Python
- HTTP
- CLI
Delete a Snapshot
- CLI
- TypeScript
- Python
- HTTP
checkpoint() Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
sandbox_id | str | — | ID of the running sandbox to snapshot |
checkpoint_type | CheckpointType (Python) / CheckpointType (TypeScript: "memory" | "filesystem") | server default (currently filesystem) | Checkpoint type. FILESYSTEM captures filesystem-only state; MEMORY captures filesystem + VM memory + running processes. |
timeout | float | 300 | Max seconds to wait for completion |
poll_interval | float | 1.0 | Seconds between status polls |
CheckpointType is exported from tensorlake.sandbox (Python) and tensorlake (TypeScript). The TypeScript field on CheckpointOptions is checkpointType.
Related Guides
Lifecycle
Create, suspend, resume, and terminate sandboxes — the operations snapshots build on.
Sandbox Images
Build reusable base images. Pair with snapshots for warm starts on top of pinned dependencies.
Computer Use
Snapshot a warmed-up
ubuntu-vnc desktop and fork parallel agent sessions.Drive Chrome over CDP
Snapshot a Chrome profile so parallel browser agents start with cookies and history already in place.