← Back to Hermes

Hermes sessions

Workflow and session operations

Use Hermes like an operator platform: continue and resume intentionally, inspect the real session inventory, and keep context clean before work gets messy.

Continuity ruleInspect the real session state before deciding Hermes lost context or that resume behavior is broken.

Once Hermes is installed and the provider/model path works, the next question is not just “how do I prompt it?” The better question is: how do I use Hermes in a way that preserves context, makes sessions findable, and keeps longer-running work from turning messy?

1. Treat workflow as staged, not magical

install and verify the runtime
start the local CLI
configure the provider/model path intentionally
run the first useful task
inspect output
repair narrowly when needed
verify again before broadening the workflow

2. Start, continue, or resume on purpose

hermes
hermes --continue / hermes -c
hermes --resume <session-id-or-title> / hermes -r <session-id-or-title>
hermes chat --continue

3. Make sessions findable early

/title My Research
/new payments-refactor
hermes sessions rename <session-id> "new title"

4. Inspect the inventory instead of guessing

hermes sessions list
hermes sessions list --source telegram
hermes sessions list --limit 50
hermes sessions browse

Practical working rules

decide early whether work belongs in a new session, the latest session, or a named prior session
inspect session inventory before assuming context loss
prefer narrow repairs over broad rebuild reactions
keep cross-surface continuity explicit as messaging surfaces are added

Related pages

Model configuration
Security and approval modes
Debugging and recovery
Validation and observability