Checkpoints & rollback

Approval gates that snapshot project state so you can roll back to a clean point.

A checkpoint is a snapshot of your project state at a specific moment — files, directory structure, and all. You take one when the agent has made good progress and you want to approve it before going further.

Why checkpoints matter

• Approval gates: pause the session, review changes, then resume confident you have a clean baseline
• Safe rollback: if the agent goes off the rails later, you can roll back to this snapshot instantly
• Context efficiency: rollback to a checkpoint lets you resume with just the necessary context — no need to reprompt the entire history

Taking a checkpoint

In the dashboard, click Take Checkpoint on the session card. vigie snapshots the current project state and stores it locally. The session pauses.

Reviewing and resuming

After you inspect the changes, you can:

• Resume the session — the agent wakes up and continues from where it left off
• Rollback — discard all changes since this checkpoint and restore the project to its snapshot state, then resume with a fresh prompt if needed

Rollback is instant because vigie keeps the snapshot in SQLite; there’s no network sync or undo stack to rebuild.

Where to next

• Supervision signals — understand what triggered the need for a checkpoint
• The dashboard — where checkpoint controls live
• Privacy & data — how snapshots are stored