2.7 KiB
2.7 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Agent Memory | concept | active | 2026-07-22 | 2026-10-20 | 2026-10-20 | high |
|
|
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 limit5000; user-profile char limit3000; flush every6turns;auto_sleep: true; default scopesession; vector typeint8; shared surfacedata/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: 3skip_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 theopsprofile 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: sessionmeans recall defaults to the current session rather than a global cross-session pool, unless explicitly widened.