Hermes Agent 会话管理指南

Neo 2026-04-16 26.5 KB 𝕏 文章列表

文章详细介绍了 Hermes Agent 的会话管理功能。Hermes 将对话视为持久化的会话，支持从 CLI、Telegram、Discord 等多平台恢复。文章阐述了会话作为“工作单元”的重要性，介绍了如何通过 ID 或标题恢复会话、利用分支功能探索不同路径，以及通过命名和整理习惯来优化工作流。

# Working With Sessions in Hermes Agent **作者**: Neo **日期**: 2026-04-15T20:35:47.000Z **来源**: [https://x.com/NeoAIForecast/status/2044515050057281808](https://x.com/NeoAIForecast/status/2044515050057281808) --- ![Image](/doc/655/image/img_9dae1b78798a.jpg) A lot of AI tools give you a conversation. Hermes gives you a session you can actually manage. That sounds small at first, but it changes a lot. Because once sessions are persistent, searchable, renameable, resumable, exportable, and organizable, Hermes starts behaving less like a disposable chat window and more like a real working environment. If you are new to Hermes, understanding sessions is one of the fastest ways to get more value out of it. ## What a session is in Hermes In Hermes, every conversation is automatically saved as a session. That includes conversations from: - CLI - Telegram - Discord - Slack - WhatsApp - Signal - Matrix - cron jobs - API/server surfaces - other supported platforms A session is not just a transcript. It is the unit Hermes uses for continuity. It tracks things like: - the message history - the title - the source platform - model and config details - timestamps - parent session relationships when a session continues through compression That means when you come back later, Hermes is not guessing what happened before. It can resume from a real stored conversation history. Takeaway: A session is Hermes’ persistent container for a conversation, not a temporary chat tab. ## Why sessions matter Most new users treat AI chats as disposable. That works for one-off questions, but it falls apart when you are doing real work: - debugging over multiple passes - writing something over several sittings - revisiting research - managing a project thread - continuing work from one device or platform to another Sessions solve that. Instead of starting over every time, you can keep a thread alive, return to it later, organize it with a name, branch it into a new direction, and search older work when you need it. This is one of the practical differences between “chatting with a model” and “working with an agent runtime.” Takeaway: Sessions are what let Hermes support continuity instead of forcing restart-by-default behavior. ## How Hermes stores sessions Hermes tracks sessions in two complementary systems. First: SQLite database at ~/.hermes/state.db This stores the structured session data, including metadata and full-text search support. Second: JSONL transcripts under ~/.hermes/sessions/ These preserve raw conversation transcripts, including tool calls in the gateway flow. In practice, what matters for users is simple: Hermes keeps both the structure and the history. So you are not only getting a visible transcript. You are getting something Hermes can list, resume, search, filter, and manage. Takeaway: Hermes sessions are real stored objects with metadata and history, not just a UI convenience. ## How to resume sessions This is one of the first session workflows new users should learn. To continue your most recent CLI session: hermes --continue or hermes -c To resume a specific session by ID: hermes --resume 20250305_091523_a1b2c3d4 To resume by title: hermes -c "my project" This is especially useful once you start naming sessions properly. Hermes also supports lineage behavior. If your session became: - my project - my project #2 - my project #3 then: hermes -c "my project" will resume the most recent one in that line. That is a very practical feature, because it means you can think in terms of project names instead of memorizing IDs. Takeaway: For day-to-day work, resume by title is usually the cleanest session habit. ## What happens when you resume When you resume a session, Hermes reloads the prior conversation history and can show a compact recap before you continue. That recap is meant to quickly reorient you: - recent user messages - recent assistant responses - collapsed tool call summaries - truncated long content - hidden internal/system noise This matters because the resume experience is not just “open old log file.” It is designed to put you back into the working thread quickly. If you want a lighter resume display, Hermes also supports a minimal mode through config. Takeaway: Resume is built for re-entry, not just archival access. ## Why naming sessions matters If you do only one thing to improve your Hermes workflow, name your important sessions. Hermes can auto-generate titles after the first exchange, and that helps. But the real upgrade is setting intentional titles yourself. Inside a session, use: /title my research project ![Image](/doc/655/image/img_dc8cd4ca5c34.jpg) From the CLI, you can rename an existing session: hermes sessions rename 20250305_091523_a1b2c3d4 "debugging auth flow" ![Image](/doc/655/image/img_31d0c0880849.jpg) A good session title makes the session easier to: - resume later - distinguish from similar conversations - organize by project - search mentally before you even search technically Bad session habit: having 40 unnamed threads that all begin with “help me…” Better session habit: naming them by project, decision, or workstream. Examples: - auth migration plan - review tasks for PR - daily recap workflow - hermes sessions article draft Takeaway: Titles turn sessions from saved chats into manageable working threads. ## How to list and browse sessions Once you have more than a handful of sessions, listing and browsing becomes important. Use: hermes sessions list You can also filter by source: hermes sessions list --source telegram Or show more: hermes sessions list --limit 50 Hermes also has: hermes sessions browse ![Image](/doc/655/image/img_22973b9fda6e.jpg) That is useful when you want a more deliberate session-picking workflow instead of remembering IDs manually. For new users, this is the practical pattern: - use sessions list when you roughly know what you want - use sessions browse when you want to inspect and choose Takeaway: Listing is for quick access. Browsing is for session management at scale. ## How to organize sessions well The simplest system is best. A good Hermes session organization strategy usually looks like this: 1. One session per real thread of work Do not pile unrelated topics into one giant conversation if you know they are separate projects. 2. Name durable threads early If the conversation will matter tomorrow, title it today. 3. Resume instead of restarting If you are continuing the same project, continue the same session. 4. Branch when you want to explore a different direction Do not wreck a clean thread just to test an alternative path. 5. Prune and export occasionally Keep your session store useful, not messy. This is less about neatness and more about keeping the agent context aligned with the work. Takeaway: Good session hygiene improves both your own recall and Hermes’ continuity. ## How branching works Branching is one of the most underappreciated session tools. Hermes includes: /branch also available as: /fork Its purpose is simple: take the current session and fork it into a new independent copy so you can explore a different path without losing the original thread. That is extremely useful when: - you want to try a different plan - you are comparing two implementations - you want a safer drafting branch - you are about to take the conversation in a very different direction Instead of mutating your main thread into a confusing hybrid, you create a branch and keep both paths clean. Takeaway: Use branch when the work is diverging, not just continuing. ## How compression affects sessions Hermes can compress context manually or automatically. When that happens, Hermes may create a continuation session in the same lineage. If the original session had a title, the follow-on sessions get numbered automatically: - my project - my project #2 - my project #3 This is important for two reasons. First, it preserves continuity without pretending the context window is infinite. Second, it keeps the lineage understandable. So if a long-running thread needs to keep going across compressed boundaries, Hermes gives you a structured continuation instead of a vague reset. Takeaway: Compression does not mean losing the thread. It means continuing it in an organized lineage. ## Best Practice for renaming sessions A few useful title rules: - titles must be unique - they are capped at 100 characters - Hermes sanitizes control characters and similar junk automatically The practical advice is: rename sessions based on the work they represent, not the first sentence you typed. Takeaway: Rename sessions around outcomes, projects, or threads of work, not random opening prompts. ## How to export sessions Sometimes you want portability, backup, or analysis. Hermes supports exporting all sessions, a filtered set, or one specific session. Examples: hermes sessions export backup.jsonl ![Image](/doc/655/image/img_6f27d825c1fb.jpg) hermes sessions export telegram-history.jsonl --source telegram hermes sessions export session.jsonl --session-id 20250305_091523_a1b2c3d4 That gives you a structured record with metadata and messages. This is useful when you want to: - back up history - move data - inspect old work outside Hermes - build your own archive - preserve a project thread before cleanup Takeaway: Export is your backup and portability layer for session history. ## How to delete and prune sessions Not every session deserves to live forever. For one specific session: hermes sessions delete 20250305_091523_a1b2c3d4 For general cleanup: hermes sessions prune hermes sessions prune --older-than 30 ![Image](/doc/655/image/img_7d5f1a0c587e.jpg) I had no older sessions than 30 days hermes sessions prune --source telegram --older-than 60 Important detail: pruning only deletes ended sessions. Active sessions are not pruned. That makes pruning safer than people often assume. The right mental model is not “delete everything old.” It is: remove stale finished threads so the session store stays manageable. Takeaway: Pruning is maintenance, not destruction. Use it to keep your session history useful. ## How to inspect session health at a high level Hermes also gives you: hermes sessions stats ![Image](/doc/655/image/img_90cf340366d6.jpg) That helps you understand things like: - total sessions - total messages - source breakdown - database size This is especially useful once Hermes becomes part of your daily workflow and you want to understand how much history is accumulating. If you want deeper usage patterns, Hermes has separate insights tooling, but sessions stats is the first health check. Takeaway: Stats helps you understand the shape of your session history before it becomes invisible clutter. ## Sessions vs session_search New users often confuse these. A session is the stored conversation itself. session_search is the retrieval layer that helps Hermes look back across past conversations. So: - sessions are the underlying stored threads - session_search is how Hermes finds relevant prior threads when needed That distinction matters because good session organization improves both your manual workflow and Hermes’ ability to retrieve useful past context later. Takeaway: Sessions are the archive. session_search is the recall mechanism. ## What new Hermes users should do first If you are just starting with Hermes, these are the session habits worth building immediately: 1. Resume ongoing work instead of starting fresh every time Use: hermes -c or hermes -c "project name" 2. Name important sessions early Use: /title my project 3. Use one session per meaningful workstream Do not mix unrelated tasks into one endless thread. 4. Branch when exploring alternatives Use: /branch 5. List and prune occasionally Use: hermes sessions list hermes sessions prune These five habits alone make Hermes feel much more coherent over time. Takeaway: Session discipline is one of the easiest ways to make Hermes more useful without changing any model settings. ## Final takeaway If skills explain how Hermes stores reusable procedures, sessions explain how Hermes stores continuity. They are the working memory structure that lets Hermes act like an environment you return to, not a blank page you reopen. For a new user, learning how to create, name, resume, branch, export, prune, and organize sessions is not optional side knowledge. It is one of the core operational habits that makes Hermes feel powerful. ## 相关链接 - [Neo](https://x.com/NeoAIForecast) - [@NeoAIForecast](https://x.com/NeoAIForecast) - [21K](https://x.com/NeoAIForecast/status/2044515050057281808/analytics) - [Upgrade to Premium](https://x.com/i/premium_sign_up) - [4:35 AM · Apr 16, 2026](https://x.com/NeoAIForecast/status/2044515050057281808) - [21.4K Views](https://x.com/NeoAIForecast/status/2044515050057281808/analytics) - [View quotes](https://x.com/NeoAIForecast/status/2044515050057281808/quotes) --- *导出时间: 2026/4/16 17:07:10* --- ## 中文翻译 # 在 Hermes Agent 中使用会话 **作者**: Neo **日期**: 2026-04-15T20:35:47.000Z **来源**: [https://x.com/NeoAIForecast/status/2044515050057281808](https://x.com/NeoAIForecast/status/2044515050057281808) --- ![Image](/doc/655/image/img_9dae1b78798a.jpg) 很多 AI 工具给你的只是一次对话。Hermes 给你的则是一个可以真正管理的会话。这听起来微不足道，但实际上意义重大。因为一旦会话可以持久化、可搜索、可重命名、可恢复、可导出、可组织管理，Hermes 的表现就不再像一个用完即弃的聊天窗口，而更像一个真正的工作环境。如果你刚接触 Hermes，理解会话是快速发挥其价值的途径之一。 ## Hermes 中什么是会话在 Hermes 中，每次对话都会自动保存为一个会话。这包括来自以下渠道的对话： - CLI - Telegram - Discord - Slack - WhatsApp - Signal - Matrix - cron 任务 - API/服务端接口 - 其他支持的平台会话不仅仅是一份对话记录。它是 Hermes 用来实现连续性的基本单元。它会追踪诸如： - 消息历史 - 标题 - 来源平台 - 模型和配置详情 - 时间戳 - 当会话经过压缩延续时的父会话关系这意味着当你稍后回来时，Hermes 不会去猜测之前发生了什么。它可以从真实存储的对话历史中恢复。要点：会话是 Hermes 为对话提供的持久化容器，而不是一个临时的聊天标签页。 ## 会话为什么重要大多数新用户把 AI 聊天当作一次性的东西。对于一次性问题这样没问题，但当你做真正的工作时就不适用了： - 多轮反复调试 - 分多次完成一篇写作 - 回顾之前的研究 - 管理一个项目线程 - 从一台设备或平台切换到另一台继续工作会话正是为此而设计的。你无需每次从头开始，而是可以让一个线程保持活跃、稍后回来继续、给它命名以便整理、把它分支到新的方向，并在需要时搜索以前的工作。这是“与模型聊天”和“与智能体运行时协作”之间的实际区别之一。要点：会话让 Hermes 能够支持连续性，而不是默认强制每次重新开始。 ## Hermes 如何存储会话 Hermes 通过两个互补的系统来追踪会话。第一：位于 ~/.hermes/state.db 的 SQLite 数据库这里存储结构化的会话数据，包括元数据和全文搜索支持。第二：位于 ~/.hermes/sessions/ 目录下的 JSONL 对话记录这些文件保留了原始的对话记录，包括网关流程中的工具调用。实际上，对用户来说重要的是很简单： Hermes 同时保存了结构和历史。所以你得到的不仅仅是一份可见的对话记录，而是 Hermes 可以列出、恢复、搜索、过滤和管理的东西。要点：Hermes 的会话是带有元数据和历史记录的真实存储对象，而不只是 UI 层面的便利功能。 ## 如何恢复会话这是新用户应该学习的第一个会话工作流程。要继续你最近的 CLI 会话： hermes --continue 或 hermes -c 要按 ID 恢复特定会话： hermes --resume 20250305_091523_a1b2c3d4 要按标题恢复： hermes -c "my project" 一旦你开始认真为会话命名，这会特别有用。 Hermes 还支持谱系行为。如果你的会话变成了： - my project - my project #2 - my project #3 那么： hermes -c "my project" 会恢复这一系列中最新的一个。这是一个非常实用的功能，因为它意味着你可以用项目名称来思考，而不必记住 ID。要点：在日常工作中，按标题恢复通常是最简洁的会话习惯。 ## 恢复时会发生什么当你恢复一个会话时，Hermes 会重新加载之前的对话历史，并可以在你继续之前显示一个简明的回顾。这个回顾的目的是让你快速重新进入状态： - 最近的用户消息 - 最近的助手回复 - 折叠的工具调用摘要 - 截断的长内容 - 隐藏的内部/系统噪音这很重要，因为恢复体验并不只是“打开旧的日志文件”。它的设计目的是让你快速回到工作线程中。如果你想要更轻量的恢复显示，Hermes 还支持通过配置启用极简模式。要点：恢复功能是为重新进入工作而设计的，而不只是用于查阅存档。 ## 为什么为会话命名很重要如果要为改善 Hermes 工作流程只做一件事，那就是为重要的会话命名。Hermes 可以在第一次交流后自动生成标题，这有帮助。但真正的提升是你自己有意识地设置标题。在会话中，使用： /title my research project ![Image](/doc/655/image/img_dc8cd4ca5c34.jpg) 在 CLI 中，你可以重命名现有会话： hermes sessions rename 20250305_091523_a1b2c3d4 "debugging auth flow" ![Image](/doc/655/image/img_31d0c0880849.jpg) 一个好的会话标题能让会话更容易： - 稍后恢复 - 与相似的对话区分开 - 按项目整理 - 在技术搜索之前先进行心理检索不好的会话习惯：有 40 个未命名的线程，全都以“帮我……”开头。更好的会话习惯：按项目、决策或工作流来命名。示例： - auth migration plan - review tasks for PR - daily recap workflow - hermes sessions article draft 要点：标题让会话从保存下来的聊天记录变成可管理的工作线程。 ## 如何列出和浏览会话一旦你的会话多了起来，列出和浏览就变得重要了。使用： hermes sessions list 你还可以按来源过滤： hermes sessions list --source telegram 或显示更多： hermes sessions list --limit 50 Hermes 还有： hermes sessions browse ![Image](/doc/655/image/img_22973b9fda6e.jpg) 当你想要一个更从容的会话挑选流程，而不是手动记住 ID 时，这很有用。对于新用户来说，实用的模式是： - 当你大致知道自己想要什么时，使用 sessions list - 当你想要查看并挑选时，使用 sessions browse 要点：列表用于快速访问。浏览用于大规模的会话管理。 ## 如何做好会话组织最简单的系统就是最好的系统。一个好的 Hermes 会话组织策略通常是这样的： 1. 每个真实的工作线索对应一个会话如果你知道它们是不同的项目，就不要把不相关的主题堆进一个巨大的对话里。 2. 尽早为长期线程命名如果这个对话明天还会重要，今天就给它起个标题。 3. 恢复而不是重新开始如果你在继续同一个项目，就继续使用同一个会话。 4. 想探索不同方向时就使用分支不要仅仅为了测试另一条路径就毁掉一个干净的线程。 5. 偶尔清理和导出保持你的会话存储有用而不是杂乱。这不在于整洁本身，而在于让代理的上下文与工作保持一致。要点：良好的会话管理习惯既能提升你自己的记忆追溯能力，也能保持 Hermes 的连续性。 ## 分支是如何工作的分支是最被低估的会话工具之一。 Hermes 提供了： /branch 也可以使用： /fork 它的目的很简单：获取当前会话并将其分叉为一个独立的新副本，这样你就可以探索不同的路径，而不会丢失原始线程。这在以下情况下极其有用： - 你想尝试一个不同的计划 - 你在比较两种实现 - 你想要一个更安全的草稿分支 - 你即将把对话带向一个完全不同的方向与其把你的主线程变成一个令人困惑的混合体，不如创建一个分支，让两条路径都保持清晰。要点：当工作在分化而不仅仅是延续时，使用 branch。 ## 压缩如何影响会话 Hermes 可以手动或自动压缩上下文。当这种情况发生时，Hermes 可能会在同一谱系中创建一个延续会话。如果原始会话有标题，后续会话会自动编号： - my project - my project #2 - my project #3 这很重要，原因有二。首先，它在延续性的同时，不会假装上下文窗口是无限的。其次，它使谱系保持清晰可辨。因此，如果一个长期运行的线程需要跨越压缩边界继续进行，Hermes 会给你一个结构化的延续，而不是一个模糊的重置。要点：压缩并不意味着丢失线程。它意味着在一个有组织的谱系中继续它。 ## 重命名会话的最佳实践一些实用的标题规则： - 标题必须唯一 - 标题最长为 100 个字符 - Hermes 会自动清理控制字符和类似的垃圾字符实用建议是：根据会话所代表的工作来重命名，而不是根据你输入的第一句话。要点：围绕成果、项目或工作线索来重命名会话，而不是随机的开场提示。 ## 如何导出会话有时你会需要可移植性、备份或分析。Hermes 支持导出所有会话、过滤后的会话集或某个特定会话。示例： hermes sessions export backup.jsonl ![Image](/doc/655/image/img_6f27d825c1fb.jpg) hermes sessions export telegram-history.jsonl --source telegram hermes sessions export session.jsonl --session-id 20250305_091523_a1b2c3d4 这样你就能得到一个包含元数据和消息的结构化记录。当你想要： - 备份历史记录 - 迁移数据 - 在 Hermes 之外检查旧的工作 - 建立自己的归档 - 在清理前保留一个项目线程时，这非常有用要点：导出是会话历史的备份和可移植层。 ## 如何删除和清理会话并不是每个会话都值得永远保留。删除某个特定会话： hermes sessions delete 20250305_091523_a1b2c3d4 进行常规清理： hermes sessions prune hermes sessions prune --older-than 30 ![Image](/doc/655/image/img_7d5f1a0c587e.jpg) 我没有超过 30 天的旧会话 hermes sessions prune --source telegram --older-than 60 重要细节：清理只会删除已结束的会话。活跃的会话不会被清理。这使得清理比人们通常想象的更安全。正确的思维模式不是“删除所有旧东西”。而是：移除陈旧的已完成线程，使会话存储保持易于管理。要点：清理是维护，不是破坏。用它来保持你的会话历史有用。 ## 如何在高层检查会话健康状况 Hermes 还提供了： hermes sessions stats ![Image](/doc/655/image/img_90cf340366d6.jpg) 这可以帮助你了解： - 会话总数 - 消息总数 - 来源分布 - 数据库大小当 Hermes 成为你日常工作流的一部分，而你想了解累积了多少历史时，这尤其有用。如果你想要更深入的使用模式分析，Hermes 有单独的洞察工具，但 sessions stats 是第一个健康检查。要点：Stats 帮助你在会话历史变成无形的杂物之前了解它的整体形态。 ## Sessions 与 session_search 的区别新用户经常混淆这两者。会话是存储的对话本身。 session_search 是检索层，帮助 Hermes 回溯查看过去的对话。所以： - sessions 是底层存储的线程 - session_search 是 Hermes 在需要时查找相关先前线程的方式这一区别很重要，因为良好的会话组织既能改善你的手动工作流，也能提升 Hermes 之后检索有用历史上下文的能力。要点：Sessions 是归档。session_search 是回忆机制。 ## 新 Hermes 用户应该首先做什么如果你刚开始使用 Hermes，以下是值得立即建立的会话习惯： 1. 恢复正在进行的工作，而不是每次都从头开始使用： hermes -c 或 hermes -c "project name" 2. 尽早为重要的会话命名使用： /title my project 3. 每个有意义的工作流使用一个会话不要把不相关的任务混进一个无休止的线程里。 4. 探索替代方案时使用分支使用： /branch 5. 偶尔列出和清理会话使用： hermes sessions list hermes sessions prune 仅这五个习惯就能让 Hermes 在长期使用中感觉更加连贯。要点：会话纪律是在不更改任何模型设置的情况下让 Hermes 更实用的最简单方法之一。 ## 最终要点如果技能解释了 Hermes 如何存储可复用的流程，那么会话就解释了 Hermes 如何存储连续性。它们是让 Hermes 像一个你可以随时回归的环境而非一页重新打开的空白纸那样运作的工作记忆结构。对于新用户来说，学习如何创建、命名、恢复、分支、导出、精简和整理会话，并不是可有可无的边缘知识。它是让 Hermes 感觉强大的核心操作习惯之一。 ## 相关链接 - [Neo](https://x.com/NeoAIForecast) - [@NeoAIForecast](https://x.com/NeoAIForecast) - [21K](https://x.com/NeoAIForecast/status/2044515050057281808/analytics) - [升级至 Premium](https://x.com/i/premium_sign_up) - [4:35 AM · Apr 16, 2026](https://x.com/NeoAIForecast/status/2044515050057281808) - [21.4K 次浏览](https://x.com/NeoAIForecast/status/2044515050057281808/analytics) - [查看引用](https://x.com/NeoAIForecast/status/2044515050057281808/quotes) --- *导出时间： 2026/4/16 17:07:10*