mnemosyne-oss/mnemosyne/mnemosyne-memory-override

Mnemosyne Memory Override

CRITICAL RULE

NEVER use the `memory` tool for durable facts.

The legacy memory system is deprecated. It has a tiny 2,200 character limit and does not use vector search. Mnemosyne is the single source of truth for all durable user data.

Mapping

When to use legacy memory (rare)

• Ephemeral session state (current todo list, temp flags)
• When Mnemosyne is explicitly confirmed down

Muscle Memory / Reflex Problem

You will reflexively reach for memory out of old habit. This is a known bug in your training. Before EVERY memory tool call, pause and ask:

"Is this durable? Would I want this next session?"

If yes → use Mnemosyne If no (temp flag, todo state) → memory is acceptable

Migration Cleanup

When moving data from legacy memory to Mnemosyne:

1. Save to Mnemosyne first with mnemosyne_remember
2. Then REMOVE the old entry from memory with memory(action="remove")
3. This prevents stale duplicates and confusion

Enforcement

If you catch yourself typing memory(action= for durable data:

1. CANCEL that tool call
2. Use Mnemosyne instead
3. Set importance >= 0.7 for anything that matters later
4. If you already polluted legacy memory, remove the entry immediately