The Locamem blog

Notes from the box.

Why agent memory should stay local, what our benchmarks actually mean, and how Locamem is built — written plainly, with the numbers attached.

May 28, 2026 · Manifesto

Memory that never leaves the box

Why we built agent memory as one local SQLite file, and why "local-first" is a security decision before it's a performance one.

May 9, 2026 · Benchmarks

Retrieval is solved. The reader isn't.

We hit 99.4% recall@10 on LongMemEval-S and ~58% end-to-end QA. The gap is the whole story, and we won't paper over it.

Coming soonDraft

Per-facet scores: retrieval you can put in front of an auditor

Every recall returns a breakdown — lexical, SimHash, recency, validity — instead of one opaque relevance number.

Coming soonDraft

We never delete: temporal validity and contradiction detection

When a fact changes, the old one isn't erased — it's marked superseded, with the contradiction logged and queryable.

Coming soonDraft

MCP-native, stdio and streamable-HTTP, in one file

How Locamem plugs into any MCP client with no daemon to babysit and no service to provision.