Use this file to discover all available pages before exploring further.
Snapshots support two snapshot types:
filesystem: captures filesystem state and restores with a cold boot.
memory: captures filesystem, memory, and running process state and restores with a warm start.
When you do not specify a type, Tensorlake uses 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.
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), entrypoint, and secrets 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).
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>.