hermes-memory-providers
Skill3.7k starsChanged 5 months agoMITView on GitHub
Install and configure Mnemosyne as a Hermes Agent memory provider — local SQLite with vector search, episodic consolidation, and temporal knowledge graphs.
- Installs packages
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- AxDSan/mnemosyneword for word, first seen Oct 8, 2026
Who's talking about mnemosyne-oss/mnemosyne
- jak119/mnemosyne-docker“Bump mnemosyne-memory from 3.15.1 to 4.0.0 in the python-dependencies group”GitHub · Nov 5, 2026
- jtstothard/hermes-tiered-memory“chore(deps-dev): update mnemosyne-memory requirement from <4.0.0,>=3.14.0 to >=3.14.0,<5.0.0”GitHub · Nov 2, 2026
- l1lchucky/chronalyn“build(deps-dev): update mnemosyne-memory requirement from <4,>=3.15 to >=3.15,<5”GitHub · Nov 2, 2026
- juanmackie/mnemosyne-hermes“provider: Update mnemosyne-memory requirement from <3.16,>=3.15.1 to >=3.15.1,<4.1 in …”GitHub · Nov 1, 2026
- AxelFooley/MnemoBrain“chore(deps): update dependency mnemosyne-memory to v4.0.0b6”GitHub · Oct 20, 2026
The biggest 5 of 21 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 21
Talked about on GitHub (21 times).
On GitHub · 21
- Nov 5, 2026Bump mnemosyne-memory from 3.15.1 to 4.0.0 in the python-dependencies group — jak119/mnemosyne-docker0 reactions
- Nov 2, 2026chore(deps-dev): update mnemosyne-memory requirement from <4.0.0,>=3.14.0 to >=3.14.0,<5.0.0 — jtstothard/hermes-tiered-memory0 reactions
- Nov 2, 2026build(deps-dev): update mnemosyne-memory requirement from <4,>=3.15 to >=3.15,<5 — l1lchucky/chronalyn0 reactions
- Nov 1, 2026provider: Update mnemosyne-memory requirement from <3.16,>=3.15.1 to >=3.15.1,<4.1 in /integrations/hermes-provider — juanmackie/mnemosyne-hermes0 reactions · 1 comment
- Oct 20, 2026chore(deps): update dependency mnemosyne-memory to v4.0.0b6 — AxelFooley/MnemoBrain0 reactions
16 more on GitHub
- Oct 17, 2026[docs] Add comparison to more comparable similar projects — indigokarasu/chronicle-agent-context-and-memory0 reactions
- Oct 15, 2026fix(ai-agent): revive mnemosyne memory (patch 0.7.4 constructor, share default bank) — DaRacci/nix-config0 reactions · 1 comment
- Oct 15, 2026[bug]: memory setup stringifies list/dict defaults; accepting mnemosyne sync_roles default silently disables capture — NousResearch/hermes-agent0 reactions · 3 comments
- Oct 12, 2026[Bug] Update disables Mnemosyne: unselected KittenTTS/core ONNX 1.29 pin conflicts with embeddings — NousResearch/hermes-agent0 reactions · 5 comments
- Oct 6, 2026feat(deps): update dependency mnemosyne-hermes ( 0.5.0 → 0.7.4 ) — 1Solon/Home-Server-Configuration0 reactions
- Oct 3, 2026chore(deps): update dependency mnemosyne-memory to v4.0.0b4 — AxelFooley/MnemoBrain0 reactions · 1 comment
- Sep 29, 2026fix(docker): reconcile selected plugin dependencies before image boot — NousResearch/hermes-agent0 reactions · 3 comments
- Sep 29, 2026Investigate the mnemosyne-oss/mnemosyne naming collision and decide whether to rename — Nabzx/mnemosyne0 reactions · 1 comment
- Sep 16, 2026Update Mnemosyne entry: new org URL — scross01/awesome-hermes-agent0 reactions
- Sep 16, 2026plugin-catalog: add mnemosyne-memory — NousResearch/hermes-agent0 reactions · 10 comments
- Sep 16, 2026[Bug]: recall loop in memory context retrieval (Mnemosyne integration) — NousResearch/hermes-agent0 reactions · 2 comments
- Sep 7, 2026fix(#914): per-write author stamps on Hermes provider writes + row-level author at consolidation — Triquetra/mnemosyne0 reactions · 1 comment
- Aug 12, 2026feat: mnemosyne — long-term memory for every Sherman — evanmotovich1-web/sherman0 reactions
- Aug 6, 2026`agent_context` is hardcoded to "primary" — provider context-skip logic (cron/flush/subagent) is dead code — NousResearch/hermes-agent0 reactions · 3 comments
- Jul 21, 2026feat(memory): add mnemosyne-oss backend for local, portable agent memory — can1357/oh-my-pi0 reactions · 3 comments
- Jul 18, 2026feat(beam): wire recall_count/last_recalled into scoring — Phase 3 of upstream #289 — sventro/mnemosyne0 reactions
Other versions1 project uses a version of this.
Word for word · 1
- AxDSan/mnemosyne★ 3.7k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- no-mistakesSkill
- mnemosyne-contextSkill
- no-mistakesSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
All without touching Hermes core — deployed purely through the plugin directory.
- Very specific: line 104
Do NOT run hermes tools disable memory — that also kills all 20 Mnemosyne-registered tools.
- Distinctive: line 114
Test in a conversation:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mnemosyne — Hermes Memory Provider
Mnemosyne is a local-first memory layer for AI agents. When deployed as a Hermes memory provider, it replaces the built-in MEMORY.md/USER.md system with SQLite-backed vector + FTS5 hybrid search, episodic consolidation, temporal knowledge graphs, and optional bidirectional sync.
100% local. Zero cloud. Sub-millisecond recall.
What It Gives You
- System prompt injection —
# Mnemosyne Memorycontext block in every prompt - Pre-turn prefetch — relevant memories injected before each LLM call
- Post-turn sync — conversation turns auto-stored to episodic memory
- 20 tools auto-injected into the model's tool surface (remember, recall, sleep, triples, scratchpad, graph, sync, diagnostics, etc.)
- 3 lifecycle hooks —
pre_llm_call,on_session_start,post_tool_call - CLI commands —
hermes mnemosyne {stats|sleep|inspect|export|import|clear|version}
All without touching Hermes core — deployed purely through the plugin directory.
Quick Check
hermes memory status # See active provider and installed pluginsInstall
Step 1 — Install the package
pip install mnemosyne-hermesDebian/Trixie users (bare pip blocked): use a venv first:
python3 -m venv ~/.hermes/hermes-agent/venv
source ~/.hermes/hermes-agent/venv/bin/activate
pip install mnemosyne-hermesmnemosyne-hermes wraps the core mnemosyne-memory library with the plugin
manifest and entry points Hermes needs. It does not pull embeddings or LLM
deps — pair it with one of:
| Extra | When | RAM |
| (core only) | Raspberry Pi, remote embedding API | ~50 MB |
mnemosyne-memory[embeddings] | Local vector search (fastembed ONNX) | ~800 MB |
mnemosyne-memory[all] | Local embeddings + local LLM consolidation | ~1.5 GB |
Step 2 — Link the plugin
mnemosyne-hermes installThis creates the symlink ~/.hermes/plugins/mnemosyne/ → <installed package>
so Hermes discovers it on startup.
Docker / read-only venv — use persistent wrapper mode so the plugin survives image rebuilds:
mnemosyne-hermes install --mode wrapper --python /path/to/venv/bin/python --hermes-home /opt/data
mnemosyne-hermes status --hermes-home /opt/data
hermes gateway restartStep 3 — Activate
hermes config set memory.provider mnemosyne
hermes memory setupStep 4 — (Optional) Disable built-in memory
Mnemosyne is additive by default — the built-in MEMORY.md/USER.md keeps
running alongside it. To make Mnemosyne the sole memory system, edit
~/.hermes/config.yaml:
memory:
memory_enabled: false
user_profile_enabled: falseDo NOT run hermes tools disable memory — that also kills all 20
Mnemosyne-registered tools.
Step 5 — Verify
hermes memory status # Should show "Provider: mnemosyne"
hermes mnemosyne stats # Working + episodic memory countsTest in a conversation:
hermes chat -q "Remember that I love apples. What do I love?"You should see mnemosyne_remember and mnemosyne_recall calls succeed.
If
hermes mnemosyne statsgives "invalid choice: 'mnemosyne'", the plugin CLI registration didn't load. Usehermes hermes-mnemosyne statsas a fallback, or re-run Step 2 to relink.
MCP vs. Provider Plugin
Mnemosyne ships an MCP server (mnemosyne mcp, stdio + SSE + Streamable HTTP
transports) that exposes 29 tools — usable with any MCP-compatible client
(Claude Desktop, etc.):
mnemosyne mcp # stdio transport
mnemosyne mcp --transport sse --port 8080 # SSE transport
mnemosyne mcp --transport streamable-http --port 8080 # native MCP http transportFor Hermes, prefer the provider plugin over MCP. The provider plugin
gives deeper integration that MCP cannot: the pre_llm_call context
injection hook, on_session_start initialization, post_tool_call memory
capture, and the hermes mnemosyne CLI subcommands. MCP is a generic
fallback for non-Hermes agents.
Switching Back
hermes memory off # Disable external provider, revert to built-in
hermes memory setup # Or use the interactive pickerOr manually:
hermes config set memory.provider memoryThen restart Hermes.
CLI Commands
hermes mnemosyne stats # Current session stats
hermes mnemosyne stats --global # Stats across all sessions
hermes mnemosyne inspect "query" # Search memories
hermes mnemosyne sleep # Run consolidation (working → episodic)
hermes mnemosyne export --output backup.json
hermes mnemosyne import --input backup.json
hermes mnemosyne clear # Clear scratchpad
hermes mnemosyne version # Show versionData Location
~/.hermes/mnemosyne/
└── data/
├── mnemosyne.db # Main SQLite database (WAL mode)
├── triples.db # Standalone TripleStore
└── banks/<name>/mnemosyne.db # Named memory banks (per-bank isolation)Persists across sessions via ~/.hermes/ (including on ephemeral VMs like Fly.io).
Optional: Host LLM Routing
Mnemosyne's consolidation (sleep) and fact extraction can use a local GGUF or
a remote OpenAI-compatible API. Hermes users with OAuth-backed providers
(e.g. openai-codex) can route those LLM calls through Hermes' authenticated
auxiliary client instead — no extra credentials needed:
export MNEMOSYNE_HOST_LLM_ENABLED=trueSee docs/hermes-llm-integration.md for the full behavior model and config.
Troubleshooting
| Symptom | Cause / Fix |
hermes memory status shows built-in only | Provider not loaded; restart Hermes after install. |
Plugin listed but unavailable | Missing Python deps in Hermes' venv; pip install mnemosyne-hermes in that venv. |
hermes mnemosyne stats → "invalid choice" | Plugin CLI registration didn't load; use hermes hermes-mnemosyne stats or relink (Step 2). |
| Memory not recalled across sessions | Provider loaded but session didn't restart; new sessions pick up the provider. |
mnemosyne_hermes import error in Docker | Use wrapper mode: mnemosyne-hermes install --mode wrapper --python <venv>/bin/python. |
References
- Hermes Integration Guide — canonical setup reference
- Hermes Auxiliary LLM Integration — host LLM routing
- Mnemosyne vs Hindsight Comparison — architecture and feature comparison
hermes-agentskill — general Hermes setup, config, and plugin system
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

