Snapshots operate at the block level of the filesystem, below anything the AI can reach. The AI can’t modify, delete, or tamper with snapshots because they exist outside its sandbox.Copy-on-write means only changed blocks are stored. A snapshot of a 10GB workspace where the AI edits one file costs kilobytes, not gigabytes.
A snapshot is taken automatically at the start of every AI turn - before the first tool call runs. If the AI makes five tool calls in one response, you get one snapshot covering the entire turn.
Each AI response in the thread shows an undo button. Clicking it restores the filesystem to the exact state before that response started. All file changes from that response are reverted.Restoring doesn’t affect the conversation history. The messages stay, but the files go back to how they were.
Snapshots cover the sandbox filesystem only. They don’t cover database changes, deployed apps, or external API calls. Destructive tools that affect those resources require approval via tool policies.
