# Hermes Agent Features and Practical Usage
🚀 Pick up exactly where you left off with a single command. Hermes Agent Sessions automatically record, resume, and search every conversation, forming the backbone of long-running agent operation.
📌 Title and Feature URL
Title: Sessions
URL:
📝 Overview
Sessions automatically save every interaction, whether from CLI, Telegram, Discord, Slack, or other platforms. Full message history is persisted to SQLite, so you can resume past work or surface old exchanges via full-text search. Because sessions are tracked per platform, each chat naturally keeps its own context.
🔧 How It Works
- History lives in `~/.hermes/state.db` (SQLite, WAL mode), tracking metadata, full message history, token counts, and an FTS5 full-text search index.
- Only the current conversation window loads into active context, not every historical byte. Images become descriptions, audio is transcribed, and documents are summarized rather than re-sent.
- After the first exchange, a background auxiliary model auto-generates a descriptive 3-7 word title with no added latency.
- Sessions are keyed deterministically by source, with distinct formats for DMs, groups, and threads.
🛠 Practical Usage
- Resume the latest CLI session: `hermes --continue` (or `-c`); resume by title with `hermes -c "project name"`, or by ID with `hermes --resume
`.
- List/export/manage: `hermes sessions list --limit 50 --source telegram`, `hermes sessions export backup.jsonl`, `hermes sessions prune --older-than 90 --yes`, `hermes sessions stats`.
- Manual naming: `/title my project` in chat, or `hermes sessions rename "new title"`.
- The agent itself uses the `session_search` tool (FTS5) and auto-references past chats when you say things like "remember when."
- Hand off an active CLI conversation to a messaging platform with `/handoff telegram`, preserving the full transcript.
🎯 Use Cases
- Resume yesterday's refactor with all prior context intact.
- Quickly recall "what did we decide back then" via full-text search.
- Keep separate context per entry point (Telegram, Discord) to avoid crosstalk.
- Use it as a work-history database for long-running agents.
⚠️ Caveats
- Auto-titling runs only once per session and skips if a title already exists.
- Media bytes are never re-sent; only derived text or file paths persist in later context.
- Auto-pruning (` is disabled by default; active sessions are never pruned regardless of age.
- On non-thread platforms with shared group home channels, genuinely shared group chats aren't handled ideally.
#HermesAgent# #AIAgents#