Hermes memory plugins come in three real flavours — swappable providers, memory-powered features like Bot Mode’s per-bot memory, and external readers like the 3D galaxy. Here’s the honest map, plus the plugin that doesn’t exist.
Short answer
- Three kinds: provider backends, memory-powered plugins, external readers of the vault.
- Bot Mode is the flagship — per-bot memory built on plain profiles, so it can’t break.
- Cloning copies memory too: weeks of training duplicated in seconds.
- No plugin fixes an empty vault — the setup comes first.
Hermes memory plugins: what that actually means
“Plugin” gets used loosely around agent memory, so let’s be precise about the three real things people mean:
- The provider layer — memory backends made swappable since the v0.7-era modular memory work. This is plumbing, and it’s covered in the provider guide.
- Plugins that use memory — features shipped as plugins whose value comes from per-agent memory.
- External layers that read it — tools outside Hermes that visualise or extend what the vault knows.
Hold that distinction and the landscape stops being confusing.
The memory plugins worth knowing
| Plugin / layer | What it does with memory |
|---|---|
| Bot Mode | Turns profiles into a roster of named bots — each with its own separate memory, so your research bot and content bot never blur |
| Cloning | Copies a bot including its memory — weeks of training duplicated to a new project in seconds |
| The memory galaxy | Renders the vault as a flyable 3D map — notes as stars, links as constellations |
| Hermes 3D’s janitor | In the community 3D office, resets sessions and cleans polluted context |
| Capture pipelines | Voice and wearable notes transcribed and filed into the vault automatically |
Bot Mode is the flagship example of memory-as-plugin done right: a bot is a profile, so its per-bot memory uses only the surface Hermes already exposes — which is why it can’t break the way bolted-on plugins do.
🔥 Want this set up without the guesswork? Plugins are only as good as the vault underneath them — that part ships ready-made. Inside the AI Profit Boardroom you get the Agent OS as a ready-to-install file, a 30-day roadmap, daily tutorials the same day new tools ship, and four live coaching calls a week where you share your screen and get unstuck. → Get access here
What doesn’t exist (and what to do instead)
- No magic recall plugin fixes an empty vault. If nothing was written down, nothing can be remembered — the setup comes first.
- No plugin should hold your secrets. Credentials don’t belong in memory at all — exports strip them by design.
- Be wary of plugins that bypass the provider. Anything storing agent knowledge in its own private silo undoes the one-brain benefit that makes memory valuable.
The test for any memory plugin: does it read and write the same markdown your agents do? If yes, it composes. If it wants its own database, it competes.
Choosing what to add first
- Nothing — until the vault itself is wired and passing the recall test.
- Bot Mode, if you run more than two jobs — per-bot memory is the cleanest separation available.
- A capture pipeline, so the vault fills from work you already do.
- Visualisation last — the galaxy is what finally makes people maintain the thing.
Recommendation logic for the underlying store is in best memory for Hermes Agent, and system-wide context in the memory system guide.
FAQ
What are Hermes memory plugins?
Three things get the name: swappable memory providers, plugins whose features run on per-agent memory (Bot Mode is the flagship), and external layers like the 3D galaxy that read the same vault.
Does Bot Mode change how memory works?
It gives every bot its own separate memory — and because a bot is just a profile, it does so using the standard profile system rather than new plumbing.
Can I clone a bot’s memory?
Yes — cloning copies config, skills, personality and memory, so a trained agent can be duplicated onto a new project with everything it learned.
Is there a plugin that fixes forgetting?
No plugin rescues an empty vault. Wire the read-and-write-back loop first; plugins extend memory, they don’t create it.
What’s the janitor?
A feature of the community Hermes 3D office that resets sessions and cleans context — useful when a session’s working memory gets polluted.
How do I judge a third-party memory plugin?
Ask whether it reads and writes the same markdown your agents use. Shared files compose; private silos quietly fork your agent’s brain.
The bottom line on Hermes memory plugins
Hermes memory plugins split into providers, memory-powered features and external readers — with Bot Mode’s per-bot memory the best of the bunch precisely because it’s just profiles underneath. Wire the vault first, add plugins that share its markdown, and refuse anything that wants a private brain of its own.
About Julian Goldie
I run Goldie Agency, a 7-figure SEO agency, and teach this daily on a 400K+ subscriber YouTube channel. 240+ client projects on Upwork at a 100% job-success score, 10+ years through every major Google update. My systems are in the AI Profit Boardroom; my link building book is free here.
Related reading
Last updated August 2026. This is the living guide to Hermes memory plugins — it gets updated as the tools change.
