M

how to build the best memory setup for Hermes:

3 min readView source ↗

Cover image

You’ve seen thousands of tutorials on memory setups making it more difficult than ever to know what is the best. That stops today. It’s time for a setup that makes your agent remember the right thing at the right time without needing to carry everything around all the time.

so I was scrolling on my timeline and I saw this:

Embedded post:

Author: Hermes Release Watch (@HermesWatcher) Post ID: 2092205452914499676 Source: https://x.com/HermesWatcher/status/2092205452914499676 Posted: 2026-08-25T11:00:25.000Z Reply to: none

Text:

> What are you using for long-term memory in your Hermes setup right now? > > Built-in memory, OpenViking, Mem0, something else? > > What made you choose it?

I then saw it had over 150 replies, so I did what any other curious autist would do - I read them - put the answers into a spreadsheet - filtered out the ai replies - and turned the replies into a tutorial to best serve the answer to this question:

“what is the best memory setup for Hermes?”

and no, this isn’t a long drawn out article, I’m going to get straight to the point and it’s simpler than you think - so if you want to implement this later make sure you bookmark this post.

1: Keep Hermes built-in memory small

> Use MEMORY.md for important long-term facts.

> Use USER.md for your preferences and personal context.

> Only keep things Hermes should always know here.

> Do not dump everything into its built-in memory.

2: Add one retrieval memory system

> Pick one: Hindsight, GBrain or Honcho.

> Use it for information Hermes should remember only when relevant.

> Let Hermes retrieve this information when a task needs it.

> Avoid putting the same information into multiple memory systems.

3: Add Obsidian for permanent records

> Create an Obsidian vault for Hermes.

> Store project notes, decisions, research and important facts there.

> Keep information organised by project or topic.

> Use this as the human-readable source of truth.

4: Easiest recommended setup

> Keep MEMORY.md + USER.md.

> Connect Hindsight.

> Use Hindsight for deeper recall and relationships.

> Add Obsidian later if you want a permanent knowledge base.

5: Best setup for shared agent knowledge

> Keep Hermes built-in memory for preferences.

> Connect GBrain as the main knowledge layer.

> Let multiple agents or machines use the same knowledge.

> Keep project-specific facts organised by source.

6: Best setup for personal modelling

> Keep Hermes built-in memory.

> Connect Honcho.

> Let Honcho learn how you think and what you prefer.

> Use Obsidian for facts and records you want to inspect yourself.

7: Simplest setup

> Keep Hermes built-in memory.

> Create an Obsidian vault.

> Put long-term project information in Obsidian.

> Let Hermes search it when needed.

> Add a retrieval provider later if recall becomes limiting.

8: Remember this if you get confused

Built-in memory = things Hermes should always know.

Retrieval memory = things Hermes should recall when relevant.

Obsidian = things you want permanently stored and readable by you.


// RESOURCES //

Built-in memory

Retrieval memory

• Provider comparison

• Hindsight setup guide

• GBrain: brain vs memory

Obsidian

• Official Obsidian skill

• Obsidian setup

Related articles