Question: how should Hermes agents handle persistent memory across sessions?
Summary
A community discussion about how Hermes agents should handle persistent memory across sessions, exploring an external memory layer (8mem) and comparing memory-aware vs generic outputs.
Similar Articles
@smykx: last month i wrote a blog on memory internals of hermes-agent by @NousResearch link in replies
The author shares a blog post detailing the memory internals of the Hermes-Agent framework developed by Nous Research.
@KSimback: https://x.com/KSimback/status/2058262328496554021
A comprehensive guide to memory systems for Hermes Agent, explaining the three-layer memory architecture and comparing various memory tools and providers.
@bayendor: Just finished wiring a 3-layer memory stack into Hermes Agent. Layer 1: Honcho Session + peer memory on PostgreSQL. Han…
Describes implementing a three-layer memory stack for Hermes Agent, combining session memory on PostgreSQL, working memory with pattern redaction, and a long-term knowledge graph using PGLite.
If you use Hermes long enough you will hit the MEMORY md wall. Here is what we did about it.
AtomicMemory is a new memory layer for the Hermes agent that replaces the 6-turn flush cycle with per-turn classification and removes the 2.2KB memory cap by storing claims in Postgres, all running on a small local 3B model.
@akshay_pachaar: the three-tier memory of Hermes agent. AI agents forgets everything when your session ends. Hermes doesn't. it has thre…
Hermes agent's three-tier memory system combines tiny always-present markdown files, full-text SQLite+FTS5 session search, and pluggable external providers to give AI agents persistent, curated memory that composes on every turn.