What does day 500 look like?

Whether Magnemo still serves a useful record at day 500 is an open question, and this page says what it covers today and what it does not.

What the mechanism gives today

Magnemo keeps its memory as a folder of plain markdown files on your computer. Four things in how it handles those files matter as the folder grows.

  • Supersession, with the old note archived. When a newer note replaces an older one, the older one is archived with its words intact. Nothing is overwritten, so you can read what the memory used to say.
  • Provenance. Every entry carries who wrote it, who approved it, and when. A trust ledger records it.
  • Your yes. Agents can only stage a note. Nothing is kept until you promote it with magnemo yes, and an agent cannot call promotion.
  • Taint never served. Notes that look like secrets or injected instructions are tainted at the door and never served to an agent, even if one is promoted by mistake. As of 0.6.7, yes refuses tainted or held notes until you run clear.

What it does not solve yet

  • Two notes that disagree. Supersession handles a note that replaces another. It does not decide between two live notes that say different things.
  • A stale note nobody re-reads. A note you approved months ago can go out of date. Nothing marks it as stale, and nothing prompts you to look at it again.
  • No benchmarks. There are no published benchmarks, so there is no measured answer to how the memory holds up over hundreds of sessions. There are no token-savings claims either.

Magnemo also does not change the model's context window or stop compaction. It gives the next session a record to boot from, which a person approved and can read.

The full list is in KNOWN_LIMITS on GitHub.