hermes

 agentmemory for Hermes Agent

Your Hermes agent remembers everything. No more re-explaining.
_{Persistent cross-session memory via agentmemory — 95.2% retrieval accuracy on LongMemEval-S. Cross-agent shared with Claude Code, Cursor, OpenCode, and more.}

---

Install it in 30 seconds

Paste this prompt into Hermes and it does the whole setup for you:

Install agentmemory for Hermes. Run `npx @agentmemory/agentmemory` in a
separate terminal to start the memory server on localhost:3111. Then
add this to `~/.hermes/config.yaml` so Hermes can use agentmemory as
an MCP server with all 43 memory tools:

mcp_servers:
  agentmemory:
    command: npx
    args: ["-y", "@agentmemory/mcp"]

memory:
  provider: agentmemory

Verify it's working with
`curl http://localhost:3111/agentmemory/health` — it should return
{"status":"healthy"}. Open the real-time viewer at
http://localhost:3113 to watch memories being captured live.

If I want deeper integration — pre-LLM context injection, turn-level
capture, memory-write mirroring to MEMORY.md, and system prompt block
injection — copy `integrations/hermes` from the agentmemory repo to
`~/.hermes/plugins/agentmemory` instead. That gives me the
6-hook memory provider plugin on top of the MCP server.

That's it. Hermes handles the rest.

Quick setup

Option 1: MCP server (zero code)

Add to ~/.hermes/config.yaml:

mcp_servers:
  agentmemory:
    command: npx
    args: ["-y", "@agentmemory/mcp"]

memory:
  provider: agentmemory

This gives Hermes access to all 43 MCP tools and enables the agentmemory memory provider. Start the server separately:

npx @agentmemory/agentmemory

Option 2: Memory provider plugin (deeper integration)

Copy this folder to your Hermes plugins directory:

cp -r integrations/hermes ~/.hermes/plugins/agentmemory

Start the agentmemory server:

npx @agentmemory/agentmemory

The plugin auto-detects the running server and hooks into the Hermes agent loop. Make sure memory.provider is set to agentmemory in ~/.hermes/config.yaml:

• prefetch() injects relevant memories before each LLM call
• sync_turn() captures every conversation turn in the background
• on_session_end() marks sessions complete for summarization
• on_pre_compress() re-injects context before compaction
• on_memory_write() mirrors MEMORY.md writes to agentmemory
• system_prompt_block() injects project profile at session start

Environment variables

Variable	Default	Description
AGENTMEMORY_URL	http://localhost:3111	agentmemory server URL
AGENTMEMORY_SECRET	(none)	Auth token for protected instances

The plugin reads ~/.agentmemory/.env (or $XDG_CONFIG_HOME/agentmemory/.env) at import time and populates any missing values into the process environment via os.environ.setdefault. Anything you set in the shell takes precedence; the file is only used to fill gaps. This means hermes memory status reports the plugin as available even when the agentmemory service is launched by systemd or another process manager that loads ~/.agentmemory/.env directly without exporting it to the Hermes CLI shell (#250).

What Hermes gets

• 95.2% retrieval accuracy (LongMemEval-S, ICLR 2025)
• Hybrid search: BM25 + vector + knowledge graph
• Memory versioning, decay, and auto-forget
• Cross-agent: memories from Claude Code, Cursor, Gemini CLI all accessible
• Real-time viewer at http://localhost:3113

How it works

Hermes has two memory files (MEMORY.md, USER.md) and SQLite full-text search. agentmemory adds structured memory on top:

Hermes built-in	agentmemory adds
MEMORY.md (flat text)	Structured observations with facts, concepts, files
USER.md (preferences)	Project profiles with top patterns and conventions
SQLite FTS5 (session search)	BM25 + vector + knowledge graph (95.2% R@5)
Skills (self-improving)	Skill extraction from completed sessions
Single agent	Cross-agent memory via MCP + REST