[{"data":1,"prerenderedAt":437},["ShallowReactive",2],{"docs-page-cn-/cn/usecase/blog/choosing_memos_integration":3,"surround-cn-/cn/usecase/blog/choosing_memos_integration":425},{"id":4,"title":5,"avatar":6,"banner":6,"body":7,"category":6,"desc":6,"description":13,"extension":419,"lead":6,"links":6,"meta":420,"navigation":6,"path":421,"seo":422,"stem":423,"__hash__":424},"docs/cn/usecase/blog/choosing_memos_integration.md","如何为 AI Agent 选择 MemOS 接入方式",null,{"type":8,"value":9,"toc":409},"minimark",[10,14,17,28,31,35,38,120,128,136,139,141,144,147,155,164,172,175,184,186,189,196,208,215,222,242,250,252,255,268,283,300,303,305,308,311,332,345,348,350,353,356,391,394,397],[11,12,13],"p",{},"假设客户在换货申请获批三天后再次联系，想知道何时发货，并提供了新的收货地址。处理这次对话的 Agent 需要此前的审批结果、更新后的地址，以及订单系统中的当前物流状态。",[11,15,16],{},"这为选择记忆系统提供了具体起点：从信息第一次出现的对话，一直追踪到后续需要它的任务。",[11,18,19,20,27],{},"我们构建 MemOS，是为了帮助应用",[21,22,26],"a",{"href":23,"rel":24},"https://memos-docs.openmem.net/cn/memos_cloud/getting_started/quick_start/",[25],"nofollow","跨对话延续上下文","。可以接入托管 API、在自己的基础设施上运行开源服务，或通过插件为支持的 Agent 添加记忆。起点取决于应用形态和运维方式。",[29,30],"br",{},[32,33,34],"h2",{"id":34},"先确定接入运行在哪里",[11,36,37],{},"团队自行开发应用时，首先选择托管服务或自行部署；为已有 Agent 环境添加记忆时，插件负责连接 Agent 与记忆系统。",[39,40,41,57],"table",{},[42,43,44],"thead",{},[45,46,47,51,54],"tr",{},[48,49,50],"th",{},"正在构建的应用",[48,52,53],{},"建议起点",[48,55,56],{},"团队负责的内容",[58,59,60,75,90,105],"tbody",{},[45,61,62,66,72],{},[63,64,65],"td",{},"需要托管记忆服务的应用",[63,67,68],{},[21,69,71],{"href":23,"rel":70},[25],"MemOS Cloud API",[63,73,74],{},"应用集成、用户身份，以及召回记忆如何进入模型上下文",[45,76,77,80,87],{},[63,78,79],{},"运行在自有基础设施上的服务",[63,81,82],{},[21,83,86],{"href":84,"rel":85},"https://github.com/MemTensor/MemOS",[25],"MemOS 开源框架",[63,88,89],{},"服务、存储依赖、模型配置与运维",[45,91,92,95,102],{},[63,93,94],{},"使用云端记忆的 OpenClaw 或 DeepSeek Harness",[63,96,97],{},[21,98,101],{"href":99,"rel":100},"https://memos-docs.openmem.net/cn/openclaw/guide/",[25],"MemOS Cloud Plugin",[63,103,104],{},"Agent 环境与插件配置",[45,106,107,110,117],{},[63,108,109],{},"使用本地记忆的 OpenClaw、Hermes Agent 或 DeepSeek Harness",[63,111,112],{},[21,113,116],{"href":114,"rel":115},"https://docs.openmem.net/cn/openclaw/local_plugin/",[25],"MemOS Local Plugin",[63,118,119],{},"本地运行环境、模型连接与备份",[11,121,122,123,127],{},"使用 MemOS Cloud 时，由我们运维记忆服务。自托管则让团队控制代码与基础设施；",[21,124,126],{"href":84,"rel":125},[25],"参考 Docker 部署","同时运行 MemOS API、Neo4j 与 Qdrant。",[11,129,130,131,135],{},"插件把记忆接入 Agent 的日常执行。MemOS Cloud Plugin 在运行前召回相关记忆，运行后保存新消息。MemOS Local Plugin 在本机维护 SQLite 存储，结合向量与词法检索，并将执行经验转化为可复用策略与技能，通过 Memory Viewer 检查结果。",[21,132,134],{"href":114,"rel":133},[25],"本地配置","包含模型连接和可选的团队共享；判断数据处理位置时，需要一并查看这些设置。",[11,137,138],{},"选定路径后，测试真正需要的工作流程。下文以 MemOS Cloud 接口为例。",[29,140],{},[32,142,143],{"id":143},"决定下一次对话需要记住什么",[11,145,146],{},"换货案例中，客户的通知偏好属于个人历史；公司的换货政策属于共享业务知识；查询订单并创建换货工单的流程，则可能被多个客户场景复用。",[11,148,149,154],{},[21,150,153],{"href":151,"rel":152},"https://memos-docs.openmem.net/cn/usecase/customer_service_assistant/",[25],"客服示例","将它们分别组织为用户记忆、Agent 技能与政策知识库。这样，Agent 可以同时检索客户背景与通用流程，并继续通过订单、工单系统获取当前业务状态。",[11,156,157,158,163],{},"MemOS Cloud 提供",[21,159,162],{"href":160,"rel":161},"https://memos-docs.openmem.net/cn/memos_cloud/introduction/memory_types/",[25],"多种记忆类型","：事实和偏好记录客户背景；事件记忆保留发生过什么；技能与工具记忆保存可复用的任务经验；属性记忆在应用需要结构化用户视图时，将信息组织到预定义字段中。",[11,165,166,167,171],{},"不同类型的准备工作有所区别。属性记忆需要为用户绑定模板，工具记忆需要输入工具调用信息，知识库需要上传内容。写入时使用 ",[168,169,170],"code",{},"allow_memory_view"," 选择允许生成的种类。",[11,173,174],{},"开发阶段，检查几个代表性对话的抽取结果。“发货时请短信通知我”是一条偏好；“如果下个月搬家，我就需要改地址”是一条带条件的陈述。测试应检查抽取后是否保留了条件。",[11,176,177,178,183],{},"需要单独检查抽取时，",[21,179,182],{"href":180,"rel":181},"https://memos-docs.openmem.net/cn/self_developed_model/extraction_usage_example/",[25],"记忆抽取接口","可以返回事实与偏好候选，而不写入记忆存储。它支持文本对话的同步抽取，便于应用检查或增加自身验证。使用完整写入流程后，也要查看实际存储的记录。",[29,185],{},[32,187,188],{"id":188},"让再次联系的客户被正确识别",[11,190,191,192,195],{},"客户从另一个渠道回来时，使用相同的 ",[168,193,194],{},"user_id","。应用从已认证的客户记录中确定这个标识。",[11,197,198,199,204,205,207],{},"MemOS Cloud 的",[21,200,203],{"href":201,"rel":202},"https://memos-docs.openmem.net/cn/memos_cloud/introduction/isolation_filters/",[25],"项目与用户范围","决定请求检索哪些个人记忆。API Key 选择项目，",[168,206,194],{}," 标识项目内客户。API Key 保留在服务端，每个请求与应用访问规则关联。",[11,209,210,211,214],{},"多个 Agent 服务同一客户时，可以用 ",[168,212,213],{},"agent_id"," 标记记忆，并按生成记忆的 Agent 过滤。Agent 也可以拥有自己的独立记忆，例如积累可复用客服技能。该行为需要在项目设置中开启「为 Agent 创建独立记忆」，默认关闭。",[11,216,217,218,221],{},"新对话仍然可以使用客户先前的记忆。",[168,219,220],{},"conversation_id"," 提供会话背景并影响相关性，不会自动将检索限制在当前会话内。",[11,223,224,229,230,233,234,237,238,241],{},[21,225,228],{"href":226,"rel":227},"https://memos-docs.openmem.net/cn/memos_cloud/mem_operations/search_memory/",[25],"检索记忆接口","结合关键词、向量检索、排序、过滤与去重。通过 ",[168,231,232],{},"include_memory_view"," 选择记忆种类，",[168,235,236],{},"memory_limit_number"," 控制结果数量，",[168,239,240],{},"filter"," 缩小范围。",[11,243,244,245,249],{},"在这个案例中，检查检索是否返回换货批准记录和相关收货信息，再检查应用实际送入模型的上下文。",[21,246,248],{"href":23,"rel":247},[25],"应用接入流程","展示了召回内容加入提示词的位置。",[29,251],{},[32,253,254],{"id":254},"处理地址变化",[11,256,257,258,263,264,267],{},"周一正确的信息，周四可能需要更新。MemOS Cloud 的",[21,259,262],{"href":260,"rel":261},"https://memos-docs.openmem.net/cn/memos_cloud/introduction/time_awareness/",[25],"时间感知机制","支持状态变化与历史问题，让当前信息和早期版本分别服务不同请求。导入旧对话时提供 ",[168,265,266],{},"chat_time","，保留信息的记录时间。",[11,269,270,271,276,277,282],{},"系统也需要纠错方式。客服团队知道具体错误条目时，可以",[21,272,275],{"href":273,"rel":274},"https://memos-docs.openmem.net/cn/memos_cloud/mem_operations/update_memory/",[25],"按记忆 ID 修改","内容、标题或状态。客户在对话中纠正时，后端可以附带用户与会话背景，通过",[21,278,281],{"href":279,"rel":280},"https://memos-docs.openmem.net/cn/memos_cloud/mem_operations/add_feedback/",[25],"自然语言反馈","提交。",[11,284,285,286,291,292,295,296,299],{},"持续跟踪到操作完成。Cloud 写入默认采用",[21,287,290],{"href":288,"rel":289},"https://memos-docs.openmem.net/cn/memos_cloud/features/async_mode/",[25],"异步处理","。使用返回的 ",[168,293,294],{},"task_id"," 查询 ",[168,297,298],{},"get/status","，完成任务包含记忆变更摘要。随后再次检索相关信息，确认下一次回答使用新地址。",[11,301,302],{},"真正发货前，应用仍应通过业务系统核实地址与订单状态。",[29,304],{},[32,306,307],{"id":307},"明确删除对象",[11,309,310],{},"客户要求删除历史信息时，先确定请求覆盖哪些记录。",[11,312,313,321,322,325,326,328,329,331],{},[21,314,317,320],{"href":315,"rel":316},"https://memos-docs.openmem.net/cn/memos_cloud/mem_operations/delete_memory/",[25],[168,318,319],{},"delete/memory"," 接口","每次接受三种目标之一：具体的 ",[168,323,324],{},"memory_ids","、",[168,327,194],{}," 或 ",[168,330,213],{},"。操作范围限定在 API Key 所属项目内，按 Agent 删除需要开启独立记忆。",[11,333,334,335,340,341,344],{},"该接口的删除目标不包含会话 ID 或知识库 ID。知识库文件使用",[21,336,339],{"href":337,"rel":338},"https://memos-docs.openmem.net/cn/api_docs/knowledge/delete_kb_doc/",[25],"独立删除接口","，传入 ",[168,342,343],{},"file_ids","。",[11,346,347],{},"删除后重复相关检索。定义完整删除流程时，一并考虑应用在缓存、导出文件或日志中保留的副本。",[29,349],{},[32,351,352],{"id":352},"推广前走完完整案例",[11,354,355],{},"试点始终围绕同一个换货场景。几种变化比一组互不相关的提示词更容易暴露集成问题。",[357,358,359,367,373,379,385],"ol",{},[360,361,362,366],"li",{},[363,364,365],"strong",{},"在新会话中返回。"," 记录审批结果后，为同一客户打开另一次对话，检查 Agent 能否接续工单，减少重复询问。",[360,368,369,372],{},[363,370,371],{},"修改细节。"," 更新收货地址，或把邮件通知改为短信，检查存储变化与下一次回答。",[360,374,375,378],{},[363,376,377],{},"加入条件陈述。"," 尝试“如果我搬到西雅图，就需要更新地址”，检查可能发生的搬家是否被误记成已确认地址变更。",[360,380,381,384],{},[363,382,383],{},"换一个客户账号。"," 以不同用户重复提问，检查请求的身份映射，并确认原客户的个人信息没有出现。",[360,386,387,390],{},[363,388,389],{},"删除测试记录。"," 删除目标记忆后再次检索。流程涉及知识库文件时，单独测试文件删除。",[11,392,393],{},"记录新信息变得可检索所需的时间，以及 p95 延迟、Token 用量和失败排查耗时。对比有无记忆时的任务结果：Agent 是否给出正确下一步，客户重复解释的次数，以及纠正是否延续到后续对话。",[11,395,396],{},"简要保存配置、结果和待解决问题，让团队能够说明所选部署为何适合应用。",[11,398,399,403,404,408],{},[21,400,402],{"href":23,"rel":401},[25],"Cloud 快速开始","介绍首次写入和检索；自行部署时，从",[21,405,407],{"href":84,"rel":406},[25],"自托管说明","开始。先完成一个客户案例，再扩展到更多工作流。",{"title":410,"searchDepth":411,"depth":411,"links":412},"",2,[413,414,415,416,417,418],{"id":34,"depth":411,"text":34},{"id":143,"depth":411,"text":143},{"id":188,"depth":411,"text":188},{"id":254,"depth":411,"text":254},{"id":307,"depth":411,"text":307},{"id":352,"depth":411,"text":352},"md",{},"/cn/usecase/blog/choosing_memos_integration",{"title":5,"description":13},"cn/usecase/blog/choosing_memos_integration","x9T30aIv0E7GohhxzOBlOWjLKwXB7gSifzGVIxIck_M",[426,432],{"title":427,"path":428,"stem":429,"framework":6,"module":6,"class":430,"target":-1,"active":431,"defaultOpen":431,"children":-1,"description":-1},"Agent 记忆可观测性：上线后值得关注的 12 项指标","/cn/usecase/blog/agent_memory_observability_12_measures","usecase/blog/agent_memory_observability_12_measures",[],false,{"title":433,"path":434,"stem":435,"framework":6,"module":6,"class":436,"target":-1,"active":431,"defaultOpen":431,"children":-1,"description":-1},"Claude 让记忆可编辑，生产 Agent 仍需要可治理的记忆层","/cn/usecase/blog/claude_editable_memory_governed_layer","usecase/blog/claude_editable_memory_governed_layer",[],1793163788582]