Snapshots
Freeze a fully set-up filesystem as a baseline, then boot new sessions from it in seconds as copy-on-write clones.
Save Snapshot
Once a session is set up the way you want, with tools installed, repos cloned, and dependencies built, Save Snapshot freezes that container's filesystem as the profile's baseline. Every new session on that profile boots from the snapshot, so there is no per-task setup. When your setup changes, update the baseline and snapshot again.
This is why snapshots replace git worktrees. Instead of juggling worktrees to give each task a clean tree, you boot a fresh session from a snapshot that already has the repo and tools in place. Every session starts from identical state, and your working copy is never involved.
Many sessions from one snapshot
New sessions are copy-on-write clones of the snapshot, so you can launch several in parallel from the same baseline. Each one runs against identical state and stays isolated from the others. That is how you fan a task out across concurrent agents.
Credentials are stripped
Credentials are stripped when a snapshot is saved, so secrets never get baked into a baseline that later sessions inherit. You bring credentials in per session instead of freezing them into the filesystem. Read more on the security page.
Related
- Profiles: the profile a snapshot belongs to.
- Containers: the runtime a snapshot lives in.