Official issues about agent memory and persistence. Sourced from the official GitHub repo; status derived from official labels; every entry links back to its source with a last-checked date.
This feature request proposes renaming memory.md to rules.md and adding configurable memory backends, since injecting all memory entries into every turn currently mixes always-needed rules with queryable facts and wastes tokens.
In cron jobs, the memory tool is exposed to the agent but fails at runtime with 'Memory is not available', because cron sessions run with skip_memory=True while still inheriting the memory tool in their default toolset.
This issue reports that memory operations bypass Hermes's hook system, making tenant isolation impossible without forking core, and proposes upstreaming a fix along with an open-source project called Hermes Swarm Map.
Using hermes chat with a custom Ollama endpoint and the local gemma4:e4b model, the agent fails to recall and use prior conversation context (such as a name the user gave it), producing inconsistent answers. Issue is closed as fixed.
This feature proposes a single-daemon architecture, inspired by OpenClaw, letting multiple Hermes agents share one gateway process with isolated per-agent workspaces and memory, routed by session key including per-topic isolation in group chats.
This feature request proposes a persistent, searchable, auto-compressing "Vault" style session memory system to replace Hermes's current transient memory, which is lost whenever a session ends or the gateway restarts.
This issue proposes adding a mempalace module to Hermes for structured external memory, providing persistent, queryable memory beyond the context window with semantic retrieval. This issue is closed.
Back to curated issues . School solution cards . Troubleshooting