Markdown Memory Beats a 382-Dependency Memory Runtime in Agent Recall Test

A developer on r/openclaw published seven months of production notes on running an agent's long-term memory as a folder of structured Markdown files instead of an installed memory runtime. The core claim: the hard part of agent memory is editorial policy, not storage or retrieval.

The break-it test

A memory startup asked the author to break their product. The benchmark: give an agent three versions of the same project decision over eight months, then check whether it can return the current version, preserve the superseded history, and show the source.

Three decisions were fed in, each tagged with the meeting it came from:

• REST — January
• GraphQL — April
• tRPC — August

Asked "what is our public API decision?", the vendor runtime returned GraphQL — the superseded answer. All three versions came back tied at a relevance score of 1.000, because nothing in the retrieval path actually reads the temporal fields. The supersession columns exist in the schema, but nothing writes to them and nothing ranks by them. Three versions of a decision become three equal facts. Install size to reach that result: 382 packages.

What the Markdown folder returned

The same class of question against the author's own memory returned the current decision, dated, with superseded versions preserved above it as struck-through history, each line carrying its source. That behavior isn't computed at query time — it's just what the file says, because the editing rules require it.

Architecture

• Long-term memory lives in structured Markdown files.
• A tiny MEMORY.md acts as a lightweight index telling the agent what exists and where to look.
• Always-loaded context stays small; persistent, inspectable memory needs no database or memory framework.
• Zero dependencies. Fully auditable with a text editor.
• Has survived seven months of daily use across three frontier models from two vendors.

The author says the full system is open source and that the README contains a single copy-paste prompt to install it on any agent with file access, but reports the subreddit's mods blocked the link.

The takeaway for anyone running a long-lived agent: if your memory layer can't return the current truth with its source while keeping the superseded versions intact, adding more retrieval infrastructure won't fix it. Editing rules will.