Multi-agent & Memory Saturday, October 17, 2026

Memory Provider Ecosystem Continues to Expand

Hermes’s pluggable memory system (introduced earlier and refined in the 0.22 cycle) now supports a growing catalog of providers. Community posts highlight Mem0 local mode, Memoria, and others. The core moved memory providers into plugins with a reviewed catalog.

Credit@sudoingX

Why it matters

Memory is no longer a one-size-fits-all choice. Builders can match backend (SQLite, knowledge graphs, vector, filesystem) to workflow without forking the agent.

From the source

Hermes Agent #memory #plugins #mem0 #pluggable-architecture

More Multi-agent & Memory

Multi-agent & MemoryOct 29

Memory plugin disabled after update (and the fix)

In v0.22.5 an update can quietly disable a memory plugin that no longer matches expectations and clear `memory.provider`. `hermes doctor` still reports healthy. Official guidance: check `hermes config get plugins.disabled`, re-enable, then re-set the provider. Fix is already merged on main.

Credit

Multi-agent & MemoryOct 27

Hermes Memory Providers & Setup

Built-in MEMORY.md / USER.md stay always on. `hermes memory setup` walks through external providers (Mem0, Honcho, Hindsight, etc.) for semantic search, knowledge graphs, and automatic fact extraction. One external provider at a time.

Credit

Multi-agent & MemoryNov 5

zeromem — Local Zero-Token Memory for Hermes

Rust-based memory system submitted to the Hermes Plugin Hackathon. Stores and searches with zero tokens, no external API, runs entirely locally. Explicitly aimed at stopping “wasting money on agent memory.”

Credit@ptaranat

Never miss a night

Every pick, delivered to your reader.

One feed for everything, or one per agent harness you run. Rebuilt every night, with full credit on every item.