跳到主要内容

会话存储

Hermes Agent 使用 SQLite 数据库(~/.hermes/state.db)来持久化会话元数据、完整消息历史记录以及模型配置,适用于 CLI 和网关会话。这取代了早期的每个会话使用 JSONL 文件的方法。

源文件:hermes_state.py

架构概览

~/.hermes/state.db (SQLite, WAL mode)
├── sessions — Session metadata, token counts, billing
├── messages — Full message history per session
├── messages_fts — FTS5 virtual table for full-text search
└── schema_version — Single-row table tracking migration state

关键设计决策:

  • WAL 模式:支持并发读取 + 单个写入者(网关多平台)
  • FTS5 虚拟表:在所有会话消息中实现快速文本搜索
  • 会话血缘关系:通过 parent_session_id 链(由上下文压缩触发的拆分)
  • 来源标签clitelegramdiscord 等):用于平台过滤
  • 批处理运行器和强化学习轨迹 不存储于此(由独立系统管理)

SQLite 模式

Sessions 表

CREATE TABLE IF NOT EXISTS sessions (
id TEXT PRIMARY KEY,
source TEXT NOT NULL,
user_id TEXT,
model TEXT,
model_config TEXT,
system_prompt TEXT,
parent_session_id TEXT,
started_at REAL NOT NULL,
ended_at REAL,
end_reason TEXT,
message_count INTEGER DEFAULT 0,
tool_call_count INTEGER DEFAULT 0,
input_tokens INTEGER DEFAULT 0,
output_tokens INTEGER DEFAULT 0,
cache_read_tokens INTEGER DEFAULT 0,
cache_write_tokens INTEGER DEFAULT 0,
reasoning_tokens INTEGER DEFAULT 0,
billing_provider TEXT,
billing_base_url TEXT,
billing_mode TEXT,
estimated_cost_usd REAL,
actual_cost_usd REAL,
cost_status TEXT,
cost_source TEXT,
pricing_version TEXT,
title TEXT,
FOREIGN KEY (parent_session_id) REFERENCES sessions(id)
);

CREATE INDEX IF NOT EXISTS idx_sessions_source ON sessions(source);
CREATE INDEX IF NOT EXISTS idx_sessions_parent ON sessions(parent_session_id);
CREATE INDEX IF NOT EXISTS idx_sessions_started ON sessions(started_at DESC);
CREATE UNIQUE INDEX IF NOT EXISTS idx_sessions_title_unique
ON sessions(title) WHERE title IS NOT NULL;

Messages 表

CREATE TABLE IF NOT EXISTS messages (
id INTEGER PRIMARY KEY AUTOINCREMENT,
session_id TEXT NOT NULL REFERENCES sessions(id),
role TEXT NOT NULL,
content TEXT,
tool_call_id TEXT,
tool_calls TEXT,
tool_name TEXT,
timestamp REAL NOT NULL,
token_count INTEGER,
finish_reason TEXT,
reasoning TEXT,
reasoning_details TEXT,
codex_reasoning_items TEXT
);

CREATE INDEX IF NOT EXISTS idx_messages_session ON messages(session_id, timestamp);

备注:

  • tool_calls 以 JSON 字符串形式存储(工具调用对象的序列化列表)
  • reasoning_detailscodex_reasoning_items 以 JSON 字符串形式存储
  • reasoning 存储提供方暴露的原始推理文本
  • 时间戳为 Unix 纪元浮点数(time.time()
CREATE VIRTUAL TABLE IF NOT EXISTS messages_fts USING fts5(
content,
content=messages,
content_rowid=id
);

FTS5 表通过三个触发器与 messages 表保持同步,这些触发器在 messages 表执行 INSERT、UPDATE 和 DELETE 操作时触发:

CREATE TRIGGER IF NOT EXISTS messages_fts_insert AFTER INSERT ON messages BEGIN
INSERT INTO messages_fts(rowid, content) VALUES (new.id, new.content);
END;

CREATE TRIGGER IF NOT EXISTS messages_fts_delete AFTER DELETE ON messages BEGIN
INSERT INTO messages_fts(messages_fts, rowid, content)
VALUES('delete', old.id, old.content);
END;

CREATE TRIGGER IF NOT EXISTS messages_fts_update AFTER UPDATE ON messages BEGIN
INSERT INTO messages_fts(messages_fts, rowid, content)
VALUES('delete', old.id, old.content);
INSERT INTO messages_fts(rowid, content) VALUES (new.id, new.content);
END;

模式版本与迁移

当前模式版本:6

schema_version 表存储一个整数。初始化时,_init_schema() 检查当前版本并按顺序应用迁移:

版本变更
1初始模式(sessions、messages、FTS5)
2在 messages 表中添加 finish_reason
3在 sessions 表中添加 title
4title 上添加唯一索引(允许 NULL,非 NULL 值必须唯一)
5添加计费列:cache_read_tokenscache_write_tokensreasoning_tokensbilling_providerbilling_base_urlbilling_modeestimated_cost_usdactual_cost_usdcost_statuscost_sourcepricing_version
6在 messages 表中添加推理列:reasoningreasoning_detailscodex_reasoning_items

每个迁移使用 ALTER TABLE ADD COLUMN 包裹在 try/except 中,以处理列已存在的情况(幂等性)。每次成功迁移后,版本号递增。

写入竞争处理

多个 hermes 进程(网关 + CLI 会话 + worktree 代理)共享一个 state.dbSessionDB 类通过以下方式处理写入竞争:

  • 短 SQLite 超时时间(1 秒),而非默认的 30 秒
  • 应用层重试,带有随机抖动(20–150ms,最多 15 次重试)
  • BEGIN IMMEDIATE 事务,使锁竞争在事务开始时即被暴露
  • 定期 WAL 检查点:每成功写入 50 次执行一次(PASSIVE 模式)

这避免了“车队效应”——即 SQLite 的确定性内部退避机制导致所有竞争写入者在同一时间间隔重试。

_WRITE_MAX_RETRIES = 15
_WRITE_RETRY_MIN_S = 0.020 # 20ms
_WRITE_RETRY_MAX_S = 0.150 # 150ms
_CHECKPOINT_EVERY_N_WRITES = 50

常见操作

初始化

from hermes_state import SessionDB

db = SessionDB() # Default: ~/.hermes/state.db
db = SessionDB(db_path=Path("/tmp/test.db")) # Custom path

创建和管理会话

# Create a new session
db.create_session(
session_id="sess_abc123",
source="cli",
model="anthropic/claude-sonnet-4.6",
user_id="user_1",
parent_session_id=None, # or previous session ID for lineage
)

# End a session
db.end_session("sess_abc123", end_reason="user_exit")

# Reopen a session (clear ended_at/end_reason)
db.reopen_session("sess_abc123")

存储消息

msg_id = db.append_message(
session_id="sess_abc123",
role="assistant",
content="Here's the answer...",
tool_calls=[{"id": "call_1", "function": {"name": "terminal", "arguments": "{}"}}],
token_count=150,
finish_reason="stop",
reasoning="Let me think about this...",
)

检索消息

# Raw messages with all metadata
messages = db.get_messages("sess_abc123")

# OpenAI conversation format (for API replay)
conversation = db.get_messages_as_conversation("sess_abc123")
# Returns: [{"role": "user", "content": "..."}, {"role": "assistant", ...}]

会话标题

# Set a title (must be unique among non-NULL titles)
db.set_session_title("sess_abc123", "Fix Docker Build")

# Resolve by title (returns most recent in lineage)
session_id = db.resolve_session_by_title("Fix Docker Build")

# Auto-generate next title in lineage
next_title = db.get_next_title_in_lineage("Fix Docker Build")
# Returns: "Fix Docker Build #2"

search_messages() 方法支持 FTS5 查询语法,并对用户输入进行自动清理。

results = db.search_messages("docker deployment")

FTS5 查询语法

语法示例含义
关键词docker deployment两个词同时匹配(隐式 AND)
引号短语"exact phrase"精确短语匹配
布尔 ORdocker OR kubernetes任一词匹配
布尔 NOTpython NOT java排除该词
前缀匹配deploy*前缀匹配
# Search only CLI sessions
results = db.search_messages("error", source_filter=["cli"])

# Exclude gateway sessions
results = db.search_messages("bug", exclude_sources=["telegram", "discord"])

# Search only user messages
results = db.search_messages("help", role_filter=["user"])

搜索结果格式

每个结果包含:

  • idsession_idroletimestamp
  • snippet — FTS5 生成的片段,包含 >>>match<<< 标记
  • context — 匹配消息前后各一条消息(内容截断至 200 字符)
  • sourcemodelsession_started — 来自父会话

_sanitize_fts5_query() 方法处理边缘情况:

  • 剥离不匹配的引号和特殊字符
  • 将连字符词用引号包裹(chat-send"chat-send"
  • 移除悬空的布尔操作符(hello ANDhello

会话血缘关系

会话可通过 parent_session_id 形成链式结构。这发生在网关中上下文压缩触发会话拆分时。

查询:查找会话血缘关系

-- Find all ancestors of a session
WITH RECURSIVE lineage AS (
SELECT * FROM sessions WHERE id = ?
UNION ALL
SELECT s.* FROM sessions s
JOIN lineage l ON s.id = l.parent_session_id
)
SELECT id, title, started_at, parent_session_id FROM lineage;

-- Find all descendants of a session
WITH RECURSIVE descendants AS (
SELECT * FROM sessions WHERE id = ?
UNION ALL
SELECT s.* FROM sessions s
JOIN descendants d ON s.parent_session_id = d.id
)
SELECT id, title, started_at FROM descendants;

查询:最近会话及预览

SELECT s.*,
COALESCE(
(SELECT SUBSTR(m.content, 1, 63)
FROM messages m
WHERE m.session_id = s.id AND m.role = 'user' AND m.content IS NOT NULL
ORDER BY m.timestamp, m.id LIMIT 1),
''
) AS preview,
COALESCE(
(SELECT MAX(m2.timestamp) FROM messages m2 WHERE m2.session_id = s.id),
s.started_at
) AS last_active
FROM sessions s
ORDER BY s.started_at DESC
LIMIT 20;

查询:令牌使用统计

-- Total tokens by model
SELECT model,
COUNT(*) as session_count,
SUM(input_tokens) as total_input,
SUM(output_tokens) as total_output,
SUM(estimated_cost_usd) as total_cost
FROM sessions
WHERE model IS NOT NULL
GROUP BY model
ORDER BY total_cost DESC;

-- Sessions with highest token usage
SELECT id, title, model, input_tokens + output_tokens AS total_tokens,
estimated_cost_usd
FROM sessions
ORDER BY total_tokens DESC
LIMIT 10;

导出与清理

# Export a single session with messages
data = db.export_session("sess_abc123")

# Export all sessions (with messages) as list of dicts
all_data = db.export_all(source="cli")

# Delete old sessions (only ended sessions)
deleted_count = db.prune_sessions(older_than_days=90)
deleted_count = db.prune_sessions(older_than_days=30, source="telegram")

# Clear messages but keep the session record
db.clear_messages("sess_abc123")

# Delete session and all messages
db.delete_session("sess_abc123")

数据库位置

默认路径:~/.hermes/state.db

该路径由 hermes_constants.get_hermes_home() 解析得出,默认为 ~/.hermes/,或由 HERMES_HOME 环境变量指定。

数据库文件、WAL 文件(state.db-wal)和共享内存文件(state.db-shm)均创建在同一个目录中。