What Persistent memory is for
Hermes documents bounded memory files for agent notes and user preferences, plus session search. These support continuity, but they are not an unlimited archive or a substitute for source material. A useful division is to store compact, reusable facts in memory and keep decisions, reports, and original evidence in project files. This makes a future session more efficient without forcing every detail into the initial prompt.
What you need
- A clearly identified Hermes profile and access to its memory and session data.
- A policy for what should persist, what is sensitive, and which source record remains authoritative.
Set it up
- 1
Start with a small set of stable facts and preferences. Ask the agent to preserve their source or project location when useful.
- 2
Keep changing status in dated project notes. Correct obsolete memory when an environment or decision changes, and confirm which profile owns the update.
Check it works
- Open a new session and ask a concrete continuity question whose answer can be checked against the project record.
- Inspect the stored state when a remembered fact appears stale; the documentation describes a session-start memory snapshot.
Limits and failure points
- Memory is bounded and can become outdated. A remembered claim still needs verification when consequences matter.
- Do not run independent writers against the same Hermes home. Separate profiles help prevent accidental mixing of personal notes and state.
Primary sources
Spotted something wrong or out of date? Tell us on X at @HermesWatcher (opens in a new tab) and we will fix it.