[{"data":1,"prerenderedAt":231},["ShallowReactive",2],{"\u002Fcn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_recall":3,"surround-\u002Fcn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_recall":216},{"id":4,"title":5,"avatar":6,"banner":6,"body":7,"category":6,"desc":209,"description":203,"extension":210,"links":6,"meta":211,"navigation":6,"path":212,"seo":213,"stem":214,"__hash__":215},"docs\u002Fcn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_recall.md","记忆召回",null,{"type":8,"value":9,"toc":202},"minimark",[10,34,36,41,44,116,118,122,125,185,187,191,194],[11,12,13,29],"warning",{},[14,15,16,24,27],"p",{},[17,18,19],"strong",{},[20,21,23],"a",{"href":22},"\u002Fapi_docs\u002Fcore\u002Fsearch_memory","直接看 API文档 点这里哦",[25,26],"br",{},[25,28],{},[14,30,31],{},[17,32,33],{},"本文聚焦于功能说明，详细接口字段及限制请点击上方文字链接查看",[25,35],{},[37,38,40],"h2",{"id":39},"_1-能力介绍","1. 能力介绍",[14,42,43],{},"记忆召回负责在用户发起新请求时，快速检索出与任务最相关的记忆片段。",[45,46,47,54,68,82],"ul",{},[48,49,50,53],"li",{},[17,51,52],{},"作用","：确保模型在生成回答时，不是“从零开始”，而是结合用户历史、偏好、上下文。",[48,55,56,59,60],{},[17,57,58],{},"返回结果","：召回的记忆包含事实 \u002F 偏好 \u002F 工具 \u002F 技能 四种类型。",[45,61,62,65],{},[48,63,64],{},"可溯源：每条记忆均附带来源、时间戳和置信度。",[48,66,67],{},"高可控：开发者可以完全掌握哪些记忆进入下游逻辑。",[48,69,70,73,74],{},[17,71,72],{},"特点","：",[45,75,76,79],{},[48,77,78],{},"无感召回：用户无需重复说明自己之前的选择或偏好",[48,80,81],{},"结构化输出：区分记忆类型，便于开发者控制是否注入",[48,83,84,73,87],{},[17,85,86],{},"功能支持",[45,88,89,96,103],{},[48,90,91,95],{},[20,92,94],{"href":93},"\u002Fmemos_cloud\u002Ffeatures\u002Fbasic\u002Ffilters","设置过滤器","：仅检索最近 30 天的对话；只要偏好类记忆，不要事实类等等",[48,97,98,102],{},[20,99,101],{"href":100},"memos_cloud\u002Fmem_operations\u002Fsearch_memory","调整召回策略","：提高相似度阈值，只返回置信度 ≥0.9 的记忆等等",[48,104,105,106,110,111,115],{},"召回基于",[20,107,109],{"href":108},"\u002Fmemos_cloud\u002Ffeatures\u002Fadvanced\u002Fknowledge_base","知识库","、",[20,112,114],{"href":113},"\u002Fmemos_cloud\u002Ffeatures\u002Fbasic\u002Fmultimodal","多模态消息","的记忆内容",[25,117],{},[37,119,121],{"id":120},"_2-进阶如果你想做深度定制","2. 进阶：如果你想做深度定制",[14,123,124],{},"在 MemOS 中，召回与补全的实现方式并非单一路径，而是由多种策略与组件组合完成。不同场景可能需要不同的配置，本节列出主要环节与可定制点，供你根据业务需要灵活选择。",[126,127,128,150],"table",{},[129,130,131],"thead",{},[132,133,134,140,145],"tr",{},[135,136,137],"th",{},[17,138,139],{},"层次",[135,141,142],{},[17,143,144],{},"可定制点",[135,146,147],{},[17,148,149],{},"示例",[151,152,153,165,175],"tbody",{},[132,154,155,159,162],{},[156,157,158],"td",{},"输出治理与审计",[156,160,161],{},"安全兜底",[156,163,164],{},"在补全指令前自动加一句「回答请遵守合规规范」",[132,166,167,169,172],{},[156,168],{},[156,170,171],{},"日志与回溯",[156,173,174],{},"每次调用记录下使用的记忆条目与 few-shot 选择",[132,176,177,179,182],{},[156,178],{},[156,180,181],{},"A\u002FB 测试",[156,183,184],{},"同时运行两套拼接模板，比较用户满意度差异",[25,186],{},[37,188,190],{"id":189},"_3-下一步行动","3. 下一步行动",[14,192,193],{},"了解MemOS更多核心能力",[45,195,196],{},[48,197,198],{},[20,199,201],{"href":200},"\u002Fmemos_cloud\u002Fintroduction\u002Fmem_lifecycle","记忆生命周期管理",{"title":203,"searchDepth":204,"depth":204,"links":205},"",2,[206,207,208],{"id":39,"depth":204,"text":40},{"id":120,"depth":204,"text":121},{"id":189,"depth":204,"text":190},"在 MemOS 中，记忆不仅仅是信息的存档，还要能够在需要时被动态取用，并转化为可执行的输入。","md",{},"\u002Fcn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_recall",{"title":5,"description":203},"cn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_recall","vLikqrWfueD2t140CT6brhycGKKBJMC3WheK0AZnLrE",[217,225],{"title":218,"path":219,"stem":220,"icon":221,"framework":6,"module":6,"class":222,"target":-1,"active":223,"defaultOpen":223,"children":-1,"description":224},"记忆调度","\u002Fcn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_schedule","memos_cloud\u002Fintroduction\u002Fmem_schedule","i-ri-calendar-line",[],false,"记忆调度就像大脑的注意力机制，动态决定在合适的时刻调用合适的记忆。",{"title":201,"path":226,"stem":227,"icon":228,"framework":6,"module":6,"class":229,"target":-1,"active":223,"defaultOpen":223,"children":-1,"description":230},"\u002Fcn\u002Fmemos_cloud\u002Fintroduction\u002Fmem_lifecycle","memos_cloud\u002Fintroduction\u002Fmem_lifecycle","i-ri-refresh-line",[],"在 MemOS 中，记忆并不是静态存放的，而是会随着时间和使用情况不断演化。",1774339745432]