Mads Thines argues that coding agents keep useful notes in incompatible files and services. He proposes a shared format so tools can exchange memories and work with the same repository context. Thines builds LoreKit, one of the tools in his comparison.
His proposed common record would describe:
- Scope and identity: where a note applies and which existing record an update changes.
- Provenance and lifetime: who or what wrote it, and when it expires.
- Shared operations: ways to read, write and search records, with tests that check whether tools preserve their contents.
Moving notes between products and letting agents access the same live address are different problems, he says. Shared memory also widens the opportunity for malicious instructions; attribution and signatures can help, but no format eliminates poisoning. This is a proposal, not an adopted standard or a measured improvement in agent performance.
The 102-comment thread on Hacker News adds practical objections.
What the thread adds
- Fordec — argues that memory lifetimes and the right abstractions remain unsettled, so standardizing now risks locking in a poor design.
- everforward — describes a simpler approach: instruct an agent in AGENTS.md to maintain a searchable knowledge-base directory.
- eladlev — asks whether parallel sessions can silently overwrite one another’s memories, and whether a shared specification should address it.
- verdverm — points out that structured metadata can help the surrounding software interpret records without spending model tokens on the job.
HN handles are pseudonymous, per-comment scores are unavailable, and ordering follows HN’s ranking. These comments are a slice of the thread, not a consensus.