创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

智能体记忆需要类OpenTelemetry标准

AI 总结

作者指出,编程智能体和AI助手分别使用AGENTS.md、CLAUDE.md、Cursor规则、Anthropic记忆工具、GitHub Copilot记忆及MCP存储,彼此难以兼容。借鉴OpenTelemetry,文章提议由中立机构制定统一规范,覆盖记忆的身份、寻址、生命周期、来源和共享访问,同时让存储、排序、嵌入与界面继续竞争。作者同时是LoreKit的开发者,因此将该项目的MIT许可模式定位为一种草案输入,而非已经完成的行业标准。

深度见解

统一的记录格式与寻址机制有望让不同智能体工具共享和迁移记忆,但这目前只是作者提出的方案,尚未形成共识。

Count the memory formats on your machine

List every place your coding tools keep something they "remember". A typical setup today:

  • an AGENTS.md or CLAUDE.md in most repos, and .cursor/rules/*.mdc in a few
  • an agent writing files to a /memories directory through Anthropic's memory tool
  • Copilot keeping facts about each repo on GitHub's side
  • a memory MCP server keeping a JSONL knowledge graph

That's four different shapes, and none of them can read the others. A lesson your CI agent learns stays in whatever wrote it. Your editor agent can't read it, and neither can the next tool you try.

Each format is reasonable on its own. Together, they rebuild the same small idea again and again: a note an agent left for its future self, stored at some address, true for a while.

And the list keeps growing. Browse r/ClaudeAI, r/LocalLLaMA or r/cursor and you'll find a steady stream of "I built a memory layer for my agent" posts, each with its own storage, its own schema and its own MCP tools. That's good evidence the problem is real: people keep hitting it badly enough to build something. But every new solution adds one more format that nothing else can read. The problem isn't a missing tool. It's a missing agreement, and that only comes from the community working on it together.

#LoreKit#OpenTelemetry#Anthropic#GitHub Copilot#Model Context Protocol#AGENTS.md#CLAUDE.md#LangGraph#Graphiti#Portable Memory#Open Memory Protocol#Mem0

原文约 8 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。