--- title: Agent Memory type: concept status: active created: 2026-07-22 updated: 2026-10-20 verified_on: 2026-10-20 confidence: high tags: [concept, memory] sources: [raw/configs/hermes-config-sanitized.txt] --- # Agent Memory ## Idea How an agent retains facts/context beyond a single conversation turn or session — what gets stored, when it's flushed, and how it's retrieved later. ## How this install implements it - **Backend:** Mnemosyne, local native (not a separate docker service) — see [[systems/mnemosyne]], [[comparisons/memory-backends]]. - **Verified settings:** memory enabled `true`; message char limit `5000`; user-profile char limit `3000`; flush every `6` turns; `auto_sleep: true`; default scope `session`; vector type `int8`; shared surface `data/shared/mnemosyne.db`. - **Correction (2026-07-22, per Anthony):** this page previously named Hindsight as a predecessor backend on this box. That was a mix-up with a different Hermes instance — Hindsight has nothing to do with this box. See [[comparisons/memory-backends]] for the full correction. > **Full `memory:` block re-read 2026-10-20 — the summary above is accurate but incomplete.** > Live values: `memory_enabled: true`, `provider: mnemosyne`, `memory_char_limit: 5000`, > `user_profile_enabled: true`, `user_char_limit: 3000`, `flush_min_turns: 6`, > `nudge_interval: 10`. Mnemosyne sub-block: `auto_sleep: true`, `default_scope: session`, > `vector_type: int8`, `sleep_threshold: 50`, `profile_isolation: true`, > `shared_surface_path: data/shared/mnemosyne.db`, `shared_surface_read: true`, > `sync_roles: [user]`, `ignore_patterns: []`. > > **New since 2026-07-22 and worth knowing:** > - `reflect.disabled_for_cron: true`, `reflect.max_calls_per_session: 3` > - **`skip_contexts: [cron, flush, subagent, background, skill_loop]`** — Mnemosyne capture is > deliberately skipped in cron, flush, subagent, background and skill-loop contexts. That is > exactly why cron runs like this one produce no Mnemosyne working memories: the skip is > configured, not a malfunction. > - `profile_isolation: true` — memories do not leak across Hermes profiles, which matters now that > the `ops` profile has been deleted (see [[runbooks/multiplexer-setup]]). ## Model - Per-turn conversation content accumulates up to the char limit, then flushes to the Mnemosyne store every 6 turns (rather than every turn) — a batching tradeoff between write frequency and losing very recent context if the process dies mid-batch. - `scope: session` means recall defaults to the current session rather than a global cross-session pool, unless explicitly widened. ## Related - [[systems/memory-backend]] - [[comparisons/memory-backends]]