Checkpoints and /rollback
Checkpoints and Hermes Agent can automatically snapshot your project before destructive operations and restore it with a single command. Checkpoints are opt in
Hermes Agent can automatically snapshot your project before destructive operations and restore it with a single command. Checkpoints are opt-in as of v2 — most users never use , and the shadow-store storage is non-trivial over time, so the default is off. …
What this page covers
- What Triggers a Checkpoint
- Quick Reference
- How Checkpoints Work
- Configuration
- Listing Checkpoints
- Inspecting the Store from the Shell
- Previewing Changes with /rollback diff
- Restoring with /rollback
- Single-File Restore
- Safety and Performance Guards
- Where Checkpoints Live
- Migration from v1
- Best Practices
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
More in Using Hermes
CLI Interface
Hermes Agent's CLI is a full terminal user interface (TUI) — not a web UI. It features multiline editing, slash command autocomplete, conversation history, inte
TUI
The TUI is the modern front end for Hermes — a terminal UI backed by the same Python runtime as the Classic CLI. Same agent, same sessions, same slash commands;
Configuration
All settings are stored in the directory for easy access. TIP — Easiest path to a working Run — one OAuth gets you a model provider and all four Tool Gateway to
Configuring Models
Configuring Models Hermes uses two kinds of model slots: Main model — what the agent thinks with. Every user message, every tool call loop, every streamed respo
Sessions
Hermes Agent automatically saves every conversation as a session. Sessions enable conversation resume, cross session search, and full conversation history manag
Profiles: Running Multiple Agents
Profiles: Running Multiple Agents Run multiple independent Hermes agents on the same machine — each with its own config, API keys, memory, sessions, skills, and