The agentic rag, wrung out.
Multi-agent & MemoryMonday, September 28, 2026
Enable `/memory approval on` so every proposed long-term memory save requires explicit approve/reject via `/memory pending`. Default is off in current docs (v0.21.5).
Prevents the agent from quietly learning incorrect or sensitive facts about the user. Essential control for production use.
Multi-agent & MemoryNov 5
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.”
Multi-agent & MemoryNov 2
Community posts (including @Daviswh summarizing @AnchorNode) detailed Grok Bot's Import Memory flow: generate prompt from settings, send to old agent, paste cleaned summary back. Warned about log bloat, accidental secret inclusion, and post-import verification with specific detail checks. Hermes side has ongoing importer work.
Multi-agent & MemoryOct 29
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.
Never miss a night
One feed for everything, or one per agent harness you run. Rebuilt every night, with full credit on every item.
