Sessions
Hermes Agent automatically saves every conversation as a session. Sessions enable conversation resume, cross session search, and full conversation history manag
- Section
- Using Hermes
- Source
- hermesbible.com/docs/user-guide/sessions
Hermes Agent automatically saves every conversation as a session. Sessions enable conversation resume, cross session search, and full conversation history manag
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- How Sessions Work
- What Counts Toward Context
- Session Sources
- CLI Session Resume
- Continue Last Session
- Resume by Name
- Resume Specific Session
- Conversation Recap on Resume
- Cross-Platform Handoff
- Session Naming
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
Section map
How Sessions Work
Maps how sessions work to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
What Counts Toward Context
Maps what counts toward context to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Session Sources
Maps session sources to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
CLI Session Resume
Maps cli session resume to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Continue Last Session
Maps continue last session to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Resume by Name
Maps resume by name to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Resume Specific Session
Maps resume specific session to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Conversation Recap on Resume
Maps conversation recap on resume to the Using Hermes documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Using Hermes doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
- Primary decision areas: How Sessions Work, What Counts Toward Context, Session Sources, CLI Session Resume, Continue Last Session. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: sessions, automatically, saves, every, conversation. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for sessions before applying exact upstream commands.
Open the source anchor for How Sessions Work and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
- Start with the source section for How Sessions Work; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for What Counts Toward Context if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.
What this page covers
- Core concept and where it fits in the Hermes Agent system.
- Setup or operating context implied by the upstream page summary.
- The source page link for full current details and updates.
Source mirror note
This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.
Open source page