Agent memory needs its OpenTelemetry moment

Coding tools often keep their own separate memory formats, each with its own storage, schema, and tools. This results in a fragmented landscape where none of the formats can read each other. The author suggests that the time is right to agree on a shared shape for agent memory. They mention a tool called LoreKit, which is open source, but stress that it is just one proposal among several.

The author draws a parallel with the history of observability vendors who all had their own agents, instrumentation libraries, and data formats before OpenTelemetry unified them. In the end, the key is that vendors agreed on what they did with the data, not on the data itself. For agent memory, the author proposes a few key questions to be answered: where the memory is true, its identity, what it says, and when it stops being true.

The author also discusses the importance of recording how memory is written, allowing signatures, and pointing at the code it depends on for verification. They argue that a shared spec is needed for agent memory, just as OpenTelemetry brought about agreement in the observability field.