Memory Providers
Memory مزوّدو النماذج
Start with meaning, then move to detail.
This lesson explains Memory Providers as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Quick Start, How It Works, Available Providers, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Memory Providers without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
External memory provider plugins — Honcho, OpenViking, Mem0, Hindsight, Holographic, RetainDB, ByteRover, Supermemory
What does the source say, and in what order?
- 01Quick Start
Start here to understand the core idea or structure.
- 02How It Works
Read this after the foundation, then connect it to the previous step.
- 03Available Providers
Read this after the foundation, then connect it to the previous step.
- 04Honcho
Read this after the foundation, then connect it to the previous step.
- 05New profile, fresh Honcho peer
Read this after the foundation, then connect it to the previous step.
- 06Existing profiles, backfill Honcho peers
Read this after the foundation, then connect it to the previous step.
- 07Per-profile observation
Read this after the foundation, then connect it to the previous step.
- 08Gateway identity mapping
Read this after the foundation, then connect it to the previous step.
- 09OpenViking
Read this after the foundation, then connect it to the previous step.
- 10Mem0
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes memory setup # interactive picker + configuration
hermes memory status # check what's active
hermes memory off # disable external providermemory:
provider: openviking # or honcho, mem0, hindsight, holographic, retaindb, byterover, supermemoryhermes memory setup # select "honcho" — runs the Honcho-specific post-setupRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.