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 mnemosyne, 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 memory-backends for the full correction.

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

• memory-backend
• memory-backends