Agent 记忆格式呼唤统一标准
推荐指数 53.0 NO. 019 · 2026.11.09
发布2026/11/08Score158Comments102
简介
当前各 AI 编码工具(Claude、Cursor、Copilot、MCP 等)的记忆数据互不兼容,形成孤岛。若 OpenTelemetry 式的统一规范出现,将打破 Agent 跨工具学习壁垒,降低多 Agent 协作的集成成本。
编辑判断
这篇文章的深层价值在于点出了一个被忽视的基础设施缺口:Agent 的可观测性(observability)已经标准化,但记忆层(state/learning)仍处于军阀割据。更关键的是,记忆互操作性比观测数据更难统一——观测是只读的,记忆涉及写入权限、隐私边界和冲突解决。
目前最接近实践的是 MCP 的 resources/prompts 机制,但它偏向工具调用而非持久记忆。如果真有标准出台,大概率会从 GitHub 的 repo-level facts 或 Anthropic 的 /memories 格式中二选一作为基底,而非从零设计。
做多 Agent 系统的团队现在就可以行动:把记忆接口抽象一层,用 JSON-LD 或类似 schema 封装,为未来兼容预留迁移路径,避免被单一工具锁死。
社区反馈
负面 98 条评论
核心争论:Agent记忆是提升效率还是引入噪音,是否应统一格式
So we need another complicated format to store information so that the machines which read unstructured text can work with it?
at this point i'm pretty convinced agent memory is strictly harmful. it remembers the wrong things, and then turns them into an inane focus for each task. i disable it universally on every harness. if i want memory, i specifically instruct the agent to record findings into a file.
Same. Everybody builds one, and then eventually realizes it makes the model stupid and confused. The right solution is pretty much always developer documentation in the repo, in roughly the same shape you'd make developer docs for humans that you want to be able to get up to speed about your codebas