How-To Series · 9: Locking It Down

Checkpoints & Rollback

A filesystem safety net for destructive operations: snapshot before the agent changes things, restore with one command.

After this videoYou can undo the agent's destructive file changes with a single command

Hermes can snapshot your project before destructive operations and restore it with /rollback. It is opt-in as of v2: enable it per session with hermes chat --checkpoints or globally via checkpoints.enabled in config.yaml. Snapshots fire before file tools and destructive shell commands, into one shared shadow git repo under ~/.hermes/checkpoints/store that never touches your real .git. In-session /rollback lists, diffs, and restores checkpoints; hermes checkpoints status/prune/clear manage the store. Guards skip oversized files and directories, auto-prune runs daily, and all errors are non-fatal.

About these resources. This episode explains Hermes checkpoints and /rollback. The Sources block names the Hermes docs page that backs every claim.

Sources · What this video distills

1 docs page · every command below traces to one of them
Primary guide
Checkpoints and /rollback
Read ↗

Commands shown · Copy and paste

each shows the source doc it came from
Enable checkpoints for one sessionfrom source ↗
hermes chat --checkpoints
Preview the diff before restoringfrom source ↗
/rollback diff 1
Sweep and trim the shadow storefrom source ↗
hermes checkpoints prune

Going deeper · Related Hermes docs

further reading · not sources of facts shown above

Next in the series · Episodes that build on this