Files
agent-estate-wiki/concepts/agent-memory.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

57 lines
3.4 KiB
Markdown

---
title: Agent Memory
type: concept
status: active
created: 2026-07-22
updated: 2026-11-11
verified_on: 2026-11-11
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]]).
> **Full `memory:` block re-read 2026-11-11 — every value unchanged.** `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: []`,
> `skip_contexts: [cron, flush, subagent, background, skill_loop]`,
> `reflect: {disabled_for_cron: true, max_calls_per_session: 3}`. The cron-skip is still why
> scheduled jobs like this stocktake leave no Mnemosyne trace.
## 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]]