Finding
Durable memory becomes powerful only when it is curated into a compact operating layer instead of becoming a second chat transcript.
Current
A typical Hermes installation may save useful facts across sessions, but memory quality often depends on the agent noticing what matters in the moment. Without a clear boundary between memory, skills, files, and session search, durable memory can fill with stale task progress, verbose notes, or facts that should have been stored as a skill or artifact instead. The weak point is not whether memory exists; it is whether it stays small, strategic, and trusted enough to influence future decisions.
Suggested
- Define the memory boundary explicitly. Exact change: Add a short “Durable memory rules” section to SOUL.md stating that memory is only for stable user preferences, environment facts, and compact pointers, while procedures go to skills, large reports go to files, and temporary task progress stays in session history.
- Add a memory hygiene step to the Optimizer Agent review loop. Exact change: Update the Optimizer Agent cron prompt or review runbook with: “Check recent memory additions for stale task progress, private details, duplicated skill content, and oversized entries; recommend prune/replace actions only when the public-safe summary remains useful.”
- Create a verification habit after significant corrections or environment discoveries. Exact change: Add a post-task checklist item to the main agent behavior prompt or relevant skill: “After user corrections, repeated workflow discoveries, or stable environment findings, decide one destination: memory, skill patch, file artifact, or no save.”
Impact
This turns Hermes memory into an operational index rather than an uncontrolled archive. The installation gains better continuity across sessions because future agents inherit the right compact facts without dragging in private or stale context. It also reduces repeated user steering: preferences, tool quirks, and stable conventions can shape behavior automatically while larger knowledge remains in the proper artifact store.
Effort
Small — this is mainly a prompt/runbook discipline change plus occasional memory pruning. The work is low-risk because it does not require changing providers, credentials, or infrastructure; it only clarifies what gets saved where.
Public page note
Safe public content includes the achievement meaning, the memory boundary model, generic examples of what belongs in durable memory, and the operational recommendation to keep memory compact. Internal-only content includes real memory entries, private user preferences, raw session excerpts, filesystem paths that expose sensitive structure, credentials, logs, and any live configuration values.