LoreKit pitches OpenTelemetry moment for agent memory
LoreKit proposes a shared, vendor-neutral format for agent memories, covering scope, identity, content, expiration, and provenance while leaving storage and ranking competitive. The goal is interoperability across coding agents, CI systems, and MCP clients. [Source](https://www.lorekit.io/blog/open-agent-memory-format)
Standardizing the memory record may matter more than standardizing another memory product, but adoption will be the hard part.
- –Scope-aware records could let lessons move between editors, CI agents, and hosted or local stores.
- –Keeping embeddings and ranking outside the spec preserves room for competing implementations.
- –Deterministic memory fits recurring coding gotchas, though lexical matching can miss paraphrases.
- –Provenance, TTLs, and archival are essential safeguards against stale or misleading lessons.
- –The OpenTelemetry analogy is compelling, but memory carries more subjective content and permission risk than telemetry.
DISCOVERED
3h ago
2026-11-08
PUBLISHED
7h ago
2026-11-08
RELEVANCE
AUTHOR
mthines