[{"data":1,"prerenderedAt":3239},["ShallowReactive",2],{"docs:operations/trusted-proxy-auth":3,"content-manifest":597},{"id":4,"title":5,"body":6,"category":579,"date":580,"description":581,"extension":582,"meta":583,"navigation":584,"path":585,"seo":586,"source":587,"sourceName":588,"sourceType":589,"stem":590,"tags":591,"updatedAt":595,"__hash__":596},"docs/docs/operations/trusted-proxy-auth.md","Trusted Proxy Auth 怎么用",{"type":7,"value":8,"toc":557},"minimark",[9,13,27,30,44,52,55,58,69,75,79,85,107,110,114,117,135,138,149,153,156,160,163,177,180,184,187,198,201,205,208,261,265,268,328,331,343,349,353,359,362,378,381,388,394,397,405,408,416,420,423,426,437,440,451,454,458,461,487,497,501,504,520,523,526,553],[10,11,5],"h1",{"id":12},"trusted-proxy-auth-怎么用",[14,15,16,17,21,22,26],"p",{},"OpenClaw 官方把 ",[18,19,20],"code",{},"trusted-proxy"," 认证模式单独做成一页，不是因为它常用，而是因为它",[23,24,25],"strong",{},"风险高但很重要","。",[14,28,29],{},"如果你只记一句话，更适合记这句：",[31,32,33,39],"ul",{},[34,35,36],"li",{},[23,37,38],{},"它适合“代理本身已经做完身份认证”的场景",[34,40,41],{},[23,42,43],{},"它不适合“只是想把 Gateway 放到 nginx / Caddy 后面”的场景",[45,46,48,49,51],"h2",{"id":47},"_1-trusted-proxy-到底做了什么","1. ",[18,50,20],{}," 到底做了什么",[14,53,54],{},"在这种模式下，Gateway 不再自己直接认证终端用户，而是把认证结果委托给前面的反向代理。",[14,56,57],{},"更准确地说，它假设：",[31,59,60,63,66],{},[34,61,62],{},"代理已经完成用户认证",[34,64,65],{},"代理会把用户身份通过 header 传给 Gateway",[34,67,68],{},"Gateway 只接受来自受信代理的请求",[14,70,71,72,26],{},"所以它不是“多一种 token 写法”，而是",[23,73,74],{},"把整套认证边界前移到代理层",[45,76,78],{"id":77},"_2-什么场景适合用","2. 什么场景适合用",[14,80,81,82,84],{},"根据官方当前文档，更适合启用 ",[18,83,20],{}," 的情况是：",[31,86,87,94,97,100],{},[34,88,89,90,93],{},"你使用 identity-aware proxy，例如 ",[18,91,92],{},"oauth2-proxy","、Pomerium、Traefik forward auth 等",[34,95,96],{},"你的反向代理就是访问 Gateway 的唯一入口",[34,98,99],{},"你在 Kubernetes / 容器环境里，需要让浏览器走统一身份系统",[34,101,102,103,106],{},"你已经遇到浏览器 WebSocket ",[18,104,105],{},"1008 unauthorized"," 之类问题，并确认需要把认证放到代理层解决",[14,108,109],{},"它更像企业或平台化部署能力，而不是个人首选。",[45,111,113],{"id":112},"_3-什么情况不该用","3. 什么情况不该用",[14,115,116],{},"官方“不建议启用”的条件写得也很明确：",[31,118,119,122,125,132],{},[34,120,121],{},"你的代理只是 TLS 终止器或普通负载均衡",[34,123,124],{},"仍然存在绕过代理直达 Gateway 的路径",[34,126,127,128,131],{},"你不确定代理是否会覆盖而不是追加 ",[18,129,130],{},"x-forwarded-*"," 头",[34,133,134],{},"你只是想“先让网页能连上再说”",[14,136,137],{},"如果是这些情况，更适合继续用：",[31,139,140,143,146],{},[34,141,142],{},"token / password auth",[34,144,145],{},"SSH tunnel",[34,147,148],{},"Tailscale Serve",[45,150,152],{"id":151},"_4-这和普通反向代理的区别","4. 这和普通反向代理的区别",[14,154,155],{},"很多人会把“反向代理 + HTTPS”和“trusted-proxy auth”混成一件事，其实不是。",[157,158,159],"h3",{"id":159},"普通反向代理",[14,161,162],{},"只负责：",[31,164,165,168,171,174],{},[34,166,167],{},"TLS",[34,169,170],{},"域名",[34,172,173],{},"路由",[34,175,176],{},"WebSocket 透传",[14,178,179],{},"这时 Gateway 自己仍然负责 token / password 认证。",[157,181,183],{"id":182},"trusted-proxy-auth","Trusted Proxy Auth",[14,185,186],{},"除了 TLS / 转发，还负责：",[31,188,189,192,195],{},[34,190,191],{},"用户登录",[34,193,194],{},"会话身份",[34,196,197],{},"用户 header 注入",[14,199,200],{},"这时 Gateway 只信代理转发来的“已经认证好的用户”。",[45,202,204],{"id":203},"_5-开启前必须过的安全检查","5. 开启前必须过的安全检查",[14,206,207],{},"官方文档现在把这几个检查项列得非常具体：",[209,210,211,220,231,242,250],"ol",{},[34,212,213,216,219],{},[23,214,215],{},"代理是唯一入口",[217,218],"br",{},"\nGateway 端口必须被防火墙保护，不能让任何人绕过代理直接访问。",[34,221,222,228,230],{},[23,223,224,227],{},[18,225,226],{},"trustedProxies"," 必须最小化",[217,229],{},"\n只写真实代理 IP，不要写整段大网段。",[34,232,233,236,238,241],{},[23,234,235],{},"代理必须覆盖 header",[217,237],{},[18,239,240],{},"X-Forwarded-For"," 等头要 overwrite，不是 append。",[34,243,244,247,249],{},[23,245,246],{},"外层用户必须走 HTTPS",[217,248],{},"\n不要在明文 HTTP 上做这层信任。",[34,251,252,258,260],{},[23,253,254,255],{},"最好显式限制 ",[18,256,257],{},"allowUsers",[217,259],{},"\n否则任何“已经被代理认证的人”都可能进 Gateway。",[45,262,264],{"id":263},"_6-一个更容易理解的最小配置","6. 一个更容易理解的最小配置",[14,266,267],{},"更适合把它理解成“三段式”：",[269,270,275],"pre",{"className":271,"code":272,"language":273,"meta":274,"style":274},"language-yaml shiki shiki-themes github-light github-dark","gateway:\n  trustedProxies:\n    - \"127.0.0.1\"\n  auth:\n    mode: trusted-proxy\n","yaml","",[18,276,277,290,298,308,316],{"__ignoreMap":274},[278,279,282,286],"span",{"class":280,"line":281},"line",1,[278,283,285],{"class":284},"s9eBZ","gateway",[278,287,289],{"class":288},"sVt8B",":\n",[278,291,293,296],{"class":280,"line":292},2,[278,294,295],{"class":284},"  trustedProxies",[278,297,289],{"class":288},[278,299,301,304],{"class":280,"line":300},3,[278,302,303],{"class":288},"    - ",[278,305,307],{"class":306},"sZZnC","\"127.0.0.1\"\n",[278,309,311,314],{"class":280,"line":310},4,[278,312,313],{"class":284},"  auth",[278,315,289],{"class":288},[278,317,319,322,325],{"class":280,"line":318},5,[278,320,321],{"class":284},"    mode",[278,323,324],{"class":288},": ",[278,326,327],{"class":306},"trusted-proxy\n",[14,329,330],{},"然后再补：",[31,332,333,336,340],{},[34,334,335],{},"代理身份 header",[34,337,338],{},[18,339,257],{},[34,341,342],{},"防火墙规则",[14,344,345,346,26],{},"也就是说，真正的重点不在 YAML 有几行，而在于",[23,347,348],{},"网络路径和用户身份是否真的闭环",[45,350,352],{"id":351},"_7-为什么官方把它标成-security-sensitive","7. 为什么官方把它标成 security-sensitive",[14,354,355,356,26],{},"因为这个模式一旦配错，风险不是“小 bug”，而是",[23,357,358],{},"整个 Gateway 被未授权访问",[14,360,361],{},"最典型的错误包括：",[31,363,364,367,372,375],{},[34,365,366],{},"代理没做认证，只做 TLS",[34,368,369,371],{},[18,370,226],{}," 写得过宽",[34,373,374],{},"Gateway 端口没有被挡住",[34,376,377],{},"用户可以自己构造 forwarded headers",[14,379,380],{},"这几类问题一旦出现，后果往往比单纯的 token 泄露更难察觉。",[45,382,384,385,387],{"id":383},"_8-allowusers-为什么很重要","8. ",[18,386,257],{}," 为什么很重要",[14,389,390,391,393],{},"官方安全检查里把空的 ",[18,392,257],{}," 也当成值得提醒的高风险项，不是没有原因。",[14,395,396],{},"因为在 trusted-proxy 模式下：",[31,398,399,402],{},[34,400,401],{},"没有限制时，任何通过代理认证的人都可能进入 Gateway",[34,403,404],{},"一旦代理接的是组织级 SSO，默认暴露面可能比你想象得大很多",[14,406,407],{},"所以更稳的做法通常是：",[31,409,410,413],{},[34,411,412],{},"先只放少量管理员 / operator",[34,414,415],{},"逐步扩大，而不是一开始全组织开放",[45,417,419],{"id":418},"_9-它和-tailscale-serve-不是一回事","9. 它和 Tailscale Serve 不是一回事",[14,421,422],{},"两者都可能出现在“浏览器连 Gateway”的场景里，但安全模型不同：",[157,424,148],{"id":425},"tailscale-serve",[31,427,428,431,434],{},[34,429,430],{},"更偏 tailnet 内部身份",[34,432,433],{},"OpenClaw 能结合本地 Tailscale daemon 校验身份",[34,435,436],{},"适合个人或小团队私网访问",[157,438,183],{"id":439},"trusted-proxy-auth-1",[31,441,442,445,448],{},[34,443,444],{},"更偏企业代理 / SSO",[34,446,447],{},"身份完全由你前面的代理决定",[34,449,450],{},"更适合统一身份和统一域名入口",[14,452,453],{},"不要把 Serve 的便利性和 trusted-proxy 的企业能力混成一类。",[45,455,457],{"id":456},"_10-最常见的排错方向","10. 最常见的排错方向",[14,459,460],{},"如果你已经开了 trusted-proxy，又遇到权限问题，优先检查：",[31,462,463,466,471,476,482],{},[34,464,465],{},"请求是不是一定经过代理",[34,467,468,469],{},"代理是不是覆盖了 ",[18,470,130],{},[34,472,473,475],{},[18,474,226],{}," 是否只包含真实代理 IP",[34,477,478,481],{},[18,479,480],{},"userHeader"," 是否和代理实际输出一致",[34,483,484,486],{},[18,485,257],{}," 是否挡住了本来想放行的人",[14,488,489,490,493,494],{},"官方文档里还特别提到，",[18,491,492],{},"openclaw security audit"," 会把 trusted-proxy auth 标成 critical 提醒，这不是报错，而是故意提醒你：",[23,495,496],{},"你把安全责任交给代理了。",[45,498,500],{"id":499},"_11-更适合的使用顺序","11. 更适合的使用顺序",[14,502,503],{},"如果你准备上 trusted-proxy，建议按这个顺序：",[209,505,506,509,512,515],{},[34,507,508],{},"先用 token / password 跑通 Gateway",[34,510,511],{},"再确认代理层认证已经稳定",[34,513,514],{},"再把 Gateway 端口完全收口到代理后面",[34,516,517,518],{},"最后才切换到 ",[18,519,20],{},[14,521,522],{},"这个顺序能明显减少“问题到底出在代理还是 Gateway”这种排错混乱。",[45,524,525],{"id":525},"下一步推荐",[31,527,528,535,541,547],{},[34,529,530],{},[531,532,534],"a",{"href":533},"/docs/operations/safety-basics","OpenClaw 安全配置基础",[34,536,537],{},[531,538,540],{"href":539},"/docs/operations/openclaw-security-best-practices","OpenClaw 安全最佳实践",[34,542,543],{},[531,544,546],{"href":545},"/docs/operations/remote-access","远程访问与 Tailscale / SSH",[34,548,549],{},[531,550,552],{"href":551},"/docs/reference/troubleshooting","故障排除与诊断思路",[554,555,556],"style",{},"html pre.shiki code .s9eBZ, html code.shiki .s9eBZ{--shiki-default:#22863A;--shiki-dark:#85E89D}html pre.shiki code .sVt8B, html code.shiki .sVt8B{--shiki-default:#24292E;--shiki-dark:#E1E4E8}html pre.shiki code .sZZnC, html code.shiki .sZZnC{--shiki-default:#032F62;--shiki-dark:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":274,"searchDepth":292,"depth":292,"links":558},[559,561,562,563,567,568,569,570,572,576,577,578],{"id":47,"depth":292,"text":560},"1. trusted-proxy 到底做了什么",{"id":77,"depth":292,"text":78},{"id":112,"depth":292,"text":113},{"id":151,"depth":292,"text":152,"children":564},[565,566],{"id":159,"depth":300,"text":159},{"id":182,"depth":300,"text":183},{"id":203,"depth":292,"text":204},{"id":263,"depth":292,"text":264},{"id":351,"depth":292,"text":352},{"id":383,"depth":292,"text":571},"8. allowUsers 为什么很重要",{"id":418,"depth":292,"text":419,"children":573},[574,575],{"id":425,"depth":300,"text":148},{"id":439,"depth":300,"text":183},{"id":456,"depth":292,"text":457},{"id":499,"depth":292,"text":500},{"id":525,"depth":292,"text":525},"运维",null,"理解 OpenClaw 的 trusted-proxy 认证模式、适用场景、风险检查项，以及它和普通 TLS 反向代理的本质区别。","md",{},true,"/docs/operations/trusted-proxy-auth",{"title":5,"description":581},"https://docs.openclaw.ai/gateway/trusted-proxy","OpenClaw Docs","official","docs/operations/trusted-proxy-auth",[20,592,593,285,594],"reverse-proxy","auth","security","2026-03-18","5QJAtdKOg7CXfH0ho5Tp-b6kkCDHVQbtNk2FhUj1ghc",{"generatedAt":598,"collections":599,"totals":3237},"2026-10-19T07:16:28.294Z",{"docs":600,"news":1818,"bestPractices":2578},{"count":601,"items":602},171,[603,616,627,635,644,649,654,661,669,677,686,693,702,711,720,727,734,740,747,754,765,773,781,791,800,809,818,827,835,842,847,855,864,872,881,889,894,901,908,916,923,932,938,948,954,959,967,974,979,989,998,1006,1014,1021,1029,1035,1040,1046,1055,1060,1065,1074,1081,1093,1099,1107,1114,1119,1126,1134,1141,1146,1152,1159,1165,1174,1180,1189,1198,1204,1209,1214,1222,1229,1235,1242,1250,1257,1263,1272,1280,1287,1294,1300,1307,1313,1322,1328,1335,1340,1349,1356,1364,1373,1378,1385,1395,1399,1405,1408,1416,1423,1430,1437,1443,1445,1450,1460,1471,1477,1483,1488,1494,1500,1507,1514,1521,1530,1537,1542,1548,1555,1564,1571,1578,1584,1590,1597,1603,1608,1613,1620,1626,1634,1640,1647,1653,1662,1668,1674,1681,1687,1693,1701,1708,1713,1721,1727,1733,1740,1747,1750,1757,1766,1773,1779,1786,1792,1798,1804,1813],{"title":604,"description":605,"path":606,"category":607,"updatedAt":608,"sourceType":609,"tags":610},"OpenClaw 核心概念","用一页建立 OpenClaw 的核心心智图，分清 Gateway、Agent、Channels、Tools、Skills、Memory 和 Control UI 各自负责什么。","/docs/getting-started/core-concepts","入门","2026-03-16","internal",[611,285,612,613,614,615],"concepts","agent","channels","tools","memory",{"title":617,"description":618,"path":619,"category":607,"updatedAt":620,"sourceType":609,"tags":621},"如果你是开发团队，应该先走哪条入口","面向开发团队和独立开发者，帮助判断应该先理解架构、配置、渠道还是扩展能力，避免刚跑通就把 OpenClaw 做成一团难维护的实验场。","/docs/getting-started/developer-team-entry","2026-03-23",[622,623,624,625,626],"developers","teams","architecture","configuration","skills",{"title":628,"description":629,"path":630,"category":607,"updatedAt":620,"sourceType":609,"tags":631},"如果你是企业运维，应该先走哪条入口","面向企业运维和长期维护者，帮助判断应该先看 Gateway、远程访问、安全还是升级治理，避免把 OpenClaw 当成一次性安装项目。","/docs/getting-started/enterprise-ops-entry",[632,633,285,594,634],"enterprise","operations","upgrades",{"title":636,"description":637,"path":638,"category":607,"updatedAt":639,"sourceType":589,"tags":640},"创建第一个 Agent","从零开始创建你的第一个 OpenClaw Agent，理解 Agent 的基本概念和配置方式。","/docs/getting-started/first-agent","2026-05-26",[612,641,642,643],"quickstart","tutorial","basics",{"title":645,"description":646,"path":647,"category":607,"updatedAt":639,"sourceType":589,"tags":648},"接入第一个渠道","学习如何将 OpenClaw Agent 接入消息渠道，实现多平台统一管理。","/docs/getting-started/first-channel",[613,641,642,643],{"title":650,"description":651,"path":652,"category":607,"updatedAt":639,"sourceType":589,"tags":653},"添加第一个技能","学习如何为 OpenClaw Agent 添加和配置技能，让助手具备更多能力。","/docs/getting-started/first-skill",[626,641,642,643],{"title":655,"description":656,"path":657,"category":607,"updatedAt":639,"sourceType":589,"tags":658},"创建第一个工作流","学习如何使用 OpenClaw 的工作流功能，实现自动化任务处理。","/docs/getting-started/first-workflow",[659,660,641,642],"workflow","automation",{"title":662,"description":663,"path":664,"category":607,"updatedAt":639,"sourceType":589,"tags":665},"快速入门","按官方推荐链路，在本机完成 OpenClaw 的安装、初始化、状态检查和第一次进入 Control UI。","/docs/getting-started/getting-started",[641,666,667,668],"installation","onboarding","dashboard",{"title":670,"description":671,"path":672,"category":607,"updatedAt":673,"sourceType":589,"tags":674},"Onboarding 引导流程说明","基于官方 Onboarding 思路，说明第一次配置 OpenClaw 时应该先做什么、后做什么，以及哪些事情不要过早展开。","/docs/getting-started/onboarding-guide","2026-03-11",[667,675,676,285],"daemon","setup",{"title":678,"description":679,"path":680,"category":607,"updatedAt":681,"sourceType":589,"tags":682},"Onboarding 的本地模式和远程模式怎么选","基于最新官方 Onboarding Wizard 文档，整理 openclaw onboard 在 local 与 remote 两种模式下分别会做什么、不会做什么，以及第一次使用更适合走哪条路。","/docs/getting-started/onboarding-local-vs-remote","2026-03-21",[667,683,684,285,685],"remote","local","wizard",{"title":687,"description":688,"path":689,"category":607,"updatedAt":620,"sourceType":609,"tags":690},"如果你是个人用户，应该先走哪条入口","面向个人重度使用者，帮助判断应该先从 Dashboard、WebChat、渠道、模型还是 Skills 开始，而不是一上来就把整套能力全部接齐。","/docs/getting-started/personal-user-entry",[691,692,668,613,626],"personal","getting-started",{"title":694,"description":695,"path":696,"category":697,"updatedAt":673,"sourceType":589,"tags":698},"如何开始系统理解 OpenClaw","给第一次接触 OpenClaw 的中文用户一条更清晰的阅读顺序，先建立整体认知，再进入安装、接入和运维细节。","/docs/getting-started/reading-path","使用指南",[699,700,701,667],"reading-path","overview","docs",{"title":703,"description":704,"path":705,"category":706,"updatedAt":707,"sourceType":589,"tags":708},"OpenClaw 是什么","用中文快速理解 OpenClaw 的定位、使用方式和它与普通聊天产品的差别。","/docs/getting-started/what-is-openclaw","产品","2026-03-13",[700,709,613,710],"self-hosted","assistant",{"title":712,"description":713,"path":714,"category":607,"updatedAt":620,"sourceType":609,"tags":715},"我什么时候再上 Skills、Plugins 和多 Agent","帮你判断现在是否已经适合进入 Skills、Plugins、Hooks 或多 Agent 扩展，而不是在基础链路未稳定时过早堆复杂度。","/docs/getting-started/when-to-add-skills-plugins-and-multi-agent",[626,716,717,718,719],"plugins","multi-agent","hooks","decision",{"title":721,"description":722,"path":723,"category":607,"updatedAt":724,"sourceType":609,"tags":725},"我什么时候该开始接入渠道","帮你判断现在是否已经适合进入 Telegram、WhatsApp、飞书等渠道接入，而不是在最小链路未稳定时过早增加复杂度。","/docs/getting-started/when-to-connect-channels","2026-03-24",[613,667,719,285,726],"safety",{"title":728,"description":729,"path":730,"category":607,"updatedAt":724,"sourceType":609,"tags":731},"模型、配置和安全这三页分别什么时候看","用最短方式判断什么时候该去看模型选择、关键配置和安全实践，避免把问题带到错误页面里越看越乱。","/docs/getting-started/when-to-read-models-config-security",[732,733,594,719,692],"models","configurations",{"title":735,"description":736,"path":737,"category":607,"updatedAt":724,"sourceType":609,"tags":738},"Dashboard、WebChat 和聊天渠道分别什么时候用","把 OpenClaw 最常见的三个使用入口拆开，帮助你判断什么时候该进 Dashboard，什么时候该用 WebChat，什么时候才值得接入 Telegram、飞书或 WhatsApp。","/docs/getting-started/when-to-use-dashboard-webchat-or-channels",[668,739,613,719,692],"webchat",{"title":741,"description":742,"path":743,"category":607,"updatedAt":724,"sourceType":609,"tags":744},"我应该先从哪个页面开始","面向第一次进入中文站的用户，按目标、角色和当前问题判断应该先看文档、学习路径、主题中心、视频还是案例。","/docs/getting-started/which-page-should-i-start-with",[692,719,701,745,746],"paths","topics",{"title":748,"description":749,"path":750,"category":706,"updatedAt":673,"sourceType":589,"tags":751},"OpenClaw 适合哪些用户","判断你是否真的需要 OpenClaw，以及它更适合哪类中文用户和团队。","/docs/getting-started/who-is-openclaw-for",[752,623,753,709],"users","scenarios",{"title":755,"description":756,"path":757,"category":758,"updatedAt":759,"sourceType":589,"tags":760},"Agent 运行时与工作区结构","理解 OpenClaw 的 Agent 运行时如何工作，工作区里每个文件是干什么的，以及如何正确配置。","/docs/manual/agent-runtime","manual","2026-06-10",[761,762,763,764],"runtime","workspace","bootstrap","sessions",{"title":766,"description":767,"path":768,"category":769,"updatedAt":673,"sourceType":770,"tags":771},"Agent 工作区结构说明","了解 OpenClaw 工作区里各类核心文件的作用，包括 AGENTS、SOUL、USER、MEMORY、日志、skills 和 sessions。","/docs/manual/agent-workspace","功能","third-party",[762,772,615,626],"soul",{"title":774,"description":775,"path":776,"category":777,"updatedAt":673,"sourceType":589,"tags":778},"Gateway 架构概览","理解 OpenClaw 的 Gateway、Control-plane 客户端和 Nodes 如何协作，以及为什么它是一个单一长连接网关系统。","/docs/manual/architecture","架构",[285,779,624,780],"nodes","control-plane",{"title":782,"description":783,"path":784,"category":769,"updatedAt":785,"sourceType":589,"tags":786},"Background Tasks、/tasks 与 task flow 应该怎么用","基于最新官方 Background Tasks 与 openclaw tasks 文档，整理 OpenClaw 的后台任务记录、/tasks 面板、通知策略和长期维护方式。","/docs/manual/background-tasks-and-task-board","2026-04-30",[787,660,788,789,790,633],"tasks","cron","subagent","cli",{"title":792,"description":793,"path":794,"category":769,"updatedAt":785,"sourceType":589,"tags":795},"Amazon Bedrock 的 AWS 凭据链与 Guardrails 应该怎么配","基于最新官方 Amazon Bedrock 文档，整理 OpenClaw 接入 Bedrock 时的凭据链、区域设置、自动发现和 Guardrails 配置重点。","/docs/manual/bedrock-guardrails-and-auth",[796,797,798,799,593,732],"bedrock","aws","providers","guardrails",{"title":801,"description":802,"path":803,"category":769,"updatedAt":804,"sourceType":589,"tags":805},"bindings 的优先级怎么影响 agent 选择","基于最新官方 Channel Routing 与 Configuration 文档，解释 peer、guild、team、account、channel 和 default agent 的命中顺序，以及为什么 binding 命中问题常常看起来像“模型选错了”。","/docs/manual/bindings-precedence-and-agent-selection","2026-03-22",[806,807,808,613,625],"bindings","routing","agents",{"title":810,"description":811,"path":812,"category":769,"updatedAt":724,"sourceType":589,"tags":813},"BlueBubbles 与 iMessage 接入","为什么官方更推荐 BlueBubbles，而不是 legacy imsg，以及远程 Mac 和 webhook 模式下该注意什么。","/docs/manual/bluebubbles-imessage",[613,814,815,816,817],"bluebubbles","imessage","macos","webhook",{"title":819,"description":820,"path":821,"category":769,"updatedAt":822,"sourceType":589,"tags":823},"Broadcast Groups 和普通 routing 的边界怎么区分","基于最新官方 Broadcast Groups 与 Channel Routing 文档，解释 Broadcast Groups 何时会生效、为什么它不是 bindings 的替代品，以及多代理同群运行时的 session、工具和响应顺序边界。","/docs/manual/broadcast-groups-and-routing-boundaries","2026-03-25",[824,807,825,808,826],"broadcast","groups","session",{"title":828,"description":829,"path":830,"category":831,"updatedAt":832,"sourceType":589,"tags":833},"Broadcast 和普通 bindings 谁先生效，什么时候该用哪一个","基于最新官方 Broadcast Groups、Channel Routing 与 Groups 文档，整理 broadcast、bindings、group policy 和 mention gating 的生效顺序，帮助团队区分“多 agent 协作”和“单 agent 路由”到底该落在哪层。","/docs/manual/broadcast-vs-binding-precedence","使用说明","2026-03-29",[824,806,807,825,834,758],"precedence",{"title":836,"description":837,"path":838,"category":769,"updatedAt":673,"sourceType":589,"tags":839},"Camera Capture 与拍照/短视频能力","理解 OpenClaw 的 camera capture 如何通过 nodes 暴露给 agent，以及设备权限和用户设置为什么比命令本身更重要。","/docs/manual/camera-capture",[840,779,841,816,612],"camera","mobile",{"title":843,"description":844,"path":845,"category":769,"updatedAt":681,"sourceType":589,"tags":846},"频道与 Session 路由怎么决定上下文边界","基于最新官方 Channel Routing 文档，整理 OpenClaw 的 session key 形状、DM/main 合并、线程隔离、binding 优先级，以及为什么 routing 不是模型自己决定的。","/docs/manual/channel-routing-and-session-keys",[807,826,613,806,825],{"title":848,"description":849,"path":850,"category":769,"updatedAt":724,"sourceType":589,"tags":851},"OpenClaw 渠道能力概览","了解 OpenClaw 当前支持的主要聊天渠道、接入方式，以及第一次应该如何选择和配置渠道。","/docs/manual/channels-overview",[613,852,853,854],"telegram","whatsapp","discord",{"title":856,"description":857,"path":858,"category":769,"updatedAt":804,"sourceType":589,"tags":859},"ClawHub 的搜索、信号和信任边界","基于最新官方 ClawHub 文档，整理技能注册表里的搜索、标签、下载信号、举报与 moderation 机制，以及中文用户挑选技能时最该看什么。","/docs/manual/clawhub-discovery-and-trust-signals",[860,626,861,862,863],"clawhub","registry","moderation","discovery",{"title":865,"description":866,"path":867,"category":769,"updatedAt":681,"sourceType":589,"tags":868},"ClawHub 的版本、锁文件和 sync 怎么理解","基于最新官方 ClawHub 文档，整理 skill bundle 的版本化、.clawhub/lock.json 的作用、sync 的扫描规则，以及为什么 ClawHub 不只是“安装站”。","/docs/manual/clawhub-versioning-and-sync",[860,626,869,870,871],"sync","lockfile","versioning",{"title":873,"description":874,"path":875,"category":769,"updatedAt":681,"sourceType":589,"tags":876},"社区插件目录怎么用","基于最新官方插件文档，整理 Community plugins 页面里最重要的筛选思路，帮助你判断哪些第三方插件值得装、哪些只适合观察。","/docs/manual/community-plugins-directory",[716,877,878,879,880],"community","ecosystem","extensions","directory",{"title":882,"description":883,"path":884,"category":831,"updatedAt":832,"sourceType":589,"tags":885},"Control UI 的 Tools 面板为什么更像运行时目录，不是静态配置页","基于最新官方 WebChat 文档，解释 Control UI `/agents` 里的 Tools 面板如何通过 tools.catalog 拉取运行时目录、何时回退到静态列表，以及为什么真正的可用性最终仍由 allow/deny 和多层策略优先级决定。","/docs/manual/control-ui-tools-catalog-and-policy-precedence",[886,614,887,888,758],"control-ui","catalog","policy",{"title":890,"description":891,"path":892,"category":607,"updatedAt":673,"sourceType":589,"tags":893},"Control UI 是什么","理解 Control UI 在 OpenClaw 中承担的角色，以及首次安装、排错和长期运行时应该如何使用它。","/docs/manual/control-ui",[668,886,285,633],{"title":895,"description":896,"path":897,"category":706,"updatedAt":673,"sourceType":589,"tags":898},"OpenClaw 核心能力总览","用一页理解 OpenClaw 当前最重要的能力结构，包括渠道、控制台、扩展和运行边界。","/docs/manual/core-capabilities",[899,613,626,900],"capabilities","voice",{"title":902,"description":903,"path":904,"category":769,"updatedAt":681,"sourceType":589,"tags":905},"Dashboard 快速打开与认证行为","基于最新官方 Dashboard 文档，整理 openclaw dashboard 的快速打开路径、token 在浏览器里的保存行为，以及本地与远程打开时最容易混淆的认证边界。","/docs/manual/dashboard-fast-path-and-auth",[668,886,593,906,907],"token","browser",{"title":909,"description":910,"path":911,"category":769,"updatedAt":681,"sourceType":589,"tags":912},"Deepgram 音频转录怎么接","基于最新官方 Deepgram provider 文档，整理 OpenClaw 里语音转录的接入方式、配置重点，以及它和聊天模型 provider 的边界。","/docs/manual/deepgram-audio-transcription",[913,914,915,900,798],"deepgram","transcription","audio",{"title":917,"description":918,"path":919,"category":769,"updatedAt":673,"sourceType":589,"tags":920},"Discord 与 Slack 接入重点","团队协作场景里，Discord 和 Slack 分别适合什么、和 Telegram/WhatsApp 的差别在哪里，以及群组响应策略该怎么收敛。","/docs/manual/discord-and-slack",[613,854,921,762,922],"slack","team",{"title":924,"description":925,"path":926,"category":769,"updatedAt":927,"sourceType":589,"tags":928},"Exec 工具、apply_patch 与执行审批","基于官方 exec、apply_patch 和 exec approvals 文档，解释高权限工具如何工作，为什么审批是硬边界，以及哪些配置最值得先看。","/docs/manual/exec-tools-and-approvals","2026-03-12",[929,930,931,614,594],"exec","apply-patch","approvals",{"title":933,"description":934,"path":935,"category":769,"updatedAt":832,"sourceType":589,"tags":936},"从 Skills 到 Workflows：OpenClaw 扩展栈完整地图","把 Skills、Tools、插件、Hooks、ClawHub、OpenProse、Lobster 和审批流程收成一张扩展地图，帮助你判断什么时候该引入哪一层复杂度。","/docs/manual/extension-stack-full-map",[626,614,716,718,937,931],"workflows",{"title":939,"description":940,"path":941,"category":769,"updatedAt":785,"sourceType":589,"tags":942},"Feishu 扫码接入、群控边界与 Drive 评论流","基于最新官方 Feishu 文档，整理 OpenClaw 2026.4.10 之后的飞书扫码接入、群聊控制、Drive 评论事件和 reply_comment 工作流。","/docs/manual/feishu-qr-login-and-drive-comments",[943,944,613,945,946,947],"feishu","lark","drive","comments","collaboration",{"title":949,"description":950,"path":951,"category":831,"updatedAt":832,"sourceType":589,"tags":952},"Telegram forum topic、群 session 和 thread key 应该怎么一起看","基于最新官方 Groups 与 Channel Routing 文档，整理 Telegram forum topic 在 OpenClaw 里的 session key 形态、topic 级上下文隔离和群触发边界，帮助团队理解“同一群里的不同 topic”为什么已经不是同一条会话。","/docs/manual/forum-topics-and-group-session-keys",[852,953,764,807,758],"forum-topics",{"title":955,"description":956,"path":957,"category":769,"updatedAt":832,"sourceType":589,"tags":958},"从第一次跑通到长期运行：OpenClaw 的完整系统地图","把安装、Gateway、控制面、渠道、模型、记忆、自动化和长期维护放到一条完整主线上，帮助你从“先跑起来”过渡到“长期稳定使用”。","/docs/manual/from-first-run-to-long-running-system",[624,285,613,732,615,660],{"title":960,"description":961,"path":962,"category":769,"updatedAt":822,"sourceType":589,"tags":963},"Headless nodes 和设备宿主边界怎么分","基于最新官方 Nodes、Architecture 与 Pairing 文档，解释 headless nodes、普通设备节点和 Gateway 之间的职责差异，帮助团队理解“能力跑在哪台机器上”这条边界。","/docs/manual/headless-node-hosts-and-device-boundaries",[779,964,965,966,285],"headless","pairing","devices",{"title":968,"description":969,"path":970,"category":769,"updatedAt":681,"sourceType":589,"tags":971},"Hooks 生命周期与事件类型","基于最新官方 Hooks 文档，解释 agent:bootstrap、session start/end、/new、/reset 等生命周期事件分别适合放什么逻辑，以及什么时候该用 hook pack 或插件托管 hooks。","/docs/manual/hook-lifecycle-events",[718,972,973,660,716],"lifecycle","events",{"title":975,"description":976,"path":977,"category":769,"updatedAt":673,"sourceType":589,"tags":978},"Hooks 能做什么","从中文用户角度理解 OpenClaw 里的 hooks，不把它只看成技术细节，而看成自动化扩展点。","/docs/manual/hooks-overview",[718,660,937,973],{"title":980,"description":981,"path":982,"category":769,"updatedAt":804,"sourceType":589,"tags":983},"消息入口的去重、合并和排队是怎么工作的","基于最新官方 Messages 文档，解释 OpenClaw 的 inbound dedupe、inbound debounce、active-run queue 和 outbound chunking 各自解决什么问题，避免把“回复慢”都误判成模型问题。","/docs/manual/inbound-dedupe-and-debounce",[984,985,986,987,988],"messages","queueing","dedupe","debounce","delivery",{"title":990,"description":991,"path":992,"category":769,"updatedAt":724,"sourceType":589,"tags":993},"本地模型支持（Ollama）","使用 Ollama 在本地运行大语言模型，实现隐私优先、零成本的 AI 助手体验。","/docs/manual/local-models-ollama",[994,995,996,997,709],"ollama","local-model","llm","privacy",{"title":999,"description":1000,"path":1001,"category":769,"updatedAt":681,"sourceType":589,"tags":1002},"节点位置能力怎么用","基于最新官方 Location Command 文档，整理 OpenClaw 的 location.get 能力、权限模式、精确位置开关，以及它和普通聊天入口的边界。","/docs/manual/location-command-nodes",[1003,779,841,1004,1005],"location","permissions","gps",{"title":1007,"description":1008,"path":1009,"category":769,"updatedAt":681,"sourceType":589,"tags":1010},"记忆文件怎么分层加载","基于最新官方 Memory 文档，整理 OpenClaw 的 daily log、MEMORY.md、memory_search 和 memory_get 各自适合存什么，以及为什么群组上下文不该直接读长期记忆。","/docs/manual/memory-files-and-loading-boundaries",[615,1011,764,1012,1013],"markdown","memory_search","memory_get",{"title":1015,"description":1016,"path":1017,"category":769,"updatedAt":724,"sourceType":589,"tags":1018},"memory plugin slot 和 Markdown source of truth 怎么配合","基于最新官方 Memory、CLI memory 与 Plugins 文档，解释为什么 OpenClaw 记忆的 source of truth 仍然是 Markdown 文件，以及 plugins.slots.memory 该怎么理解和切换。","/docs/manual/memory-plugin-slots-and-source-of-truth",[615,716,1019,1020,1011],"lancedb","memory-core",{"title":1022,"description":1023,"path":1024,"category":769,"updatedAt":927,"sourceType":589,"tags":1025},"记忆搜索与索引机制","基于官方记忆概念和 memory CLI 文档，解释记忆文件、索引来源、provider 选择以及排障时该看什么。","/docs/manual/memory-search-and-indexing",[615,1026,1027,1028,1019],"search","indexing","embeddings",{"title":1030,"description":1031,"path":1032,"category":769,"updatedAt":673,"sourceType":770,"tags":1033},"OpenClaw 记忆系统怎么工作","理解 OpenClaw 的 SOUL、Tools、用户长期记忆和会话上下文如何协作，以及为什么它更像持续运行的系统而不是一次性聊天窗口。","/docs/manual/memory-system",[615,772,826,1034],"logs",{"title":1036,"description":1037,"path":1038,"category":769,"updatedAt":673,"sourceType":589,"tags":1039},"Memory、Tools、Skills 如何协同","记忆层负责保留什么，Tools 负责执行什么，Skills 负责组织什么，三者该怎么分工才不会让 OpenClaw 越用越乱。","/docs/manual/memory-tools-skills-playbook",[615,614,626,772,659],{"title":1041,"description":1042,"path":1043,"category":769,"updatedAt":927,"sourceType":589,"tags":1044},"消息投递、重试与响应行为","基于官方 retry、messages 和 FAQ 文档，解释消息发送失败时 OpenClaw 会重试什么，不会重试什么，以及为什么群聊和渠道行为会不同。","/docs/manual/message-retries-and-delivery",[984,1045,988,852,854],"retry",{"title":1047,"description":1048,"path":1049,"category":831,"updatedAt":832,"sourceType":589,"tags":1050},"模型 allowlist、alias 和图片能力门控应该怎么理解","基于最新官方 Models CLI 文档，整理 agents.defaults.models、primary、fallbacks、imageModel 和 imageGenerationModel 的职责，帮助团队理解模型白名单和共享能力门控到底会影响什么。","/docs/manual/model-allowlists-and-capability-gating",[732,1051,1052,1053,1054,758],"allowlist","aliases","image","gating",{"title":1056,"description":1057,"path":1058,"category":769,"updatedAt":724,"sourceType":589,"tags":1059},"OpenClaw 的 Models 应该怎么理解","理解 OpenClaw 里模型层的角色、选择思路和常见配置边界，避免把所有问题都误判成模型问题。","/docs/manual/models-overview",[732,996,798,807],{"title":1061,"description":1062,"path":1063,"category":769,"updatedAt":673,"sourceType":589,"tags":1064},"Nodes 与设备能力","理解 OpenClaw 的 nodes 是什么、如何配对，以及相机、语音、屏幕、位置等设备能力在系统里的作用。","/docs/manual/nodes-and-device-actions",[779,841,840,900,965],{"title":1066,"description":1067,"path":1068,"category":758,"updatedAt":759,"sourceType":589,"tags":1069},"OAuth 认证与多账号管理","理解 OpenClaw 如何处理 OAuth 认证、Token 存储和多账号路由，以及常见问题排查。","/docs/manual/oauth-auth",[1070,593,1071,1072,1073],"oauth","codex","claude","profiles",{"title":1075,"description":1076,"path":1077,"category":769,"updatedAt":724,"sourceType":589,"tags":1078},"OpenProse 和 Lobster 的边界怎么分","基于最新官方 Lobster 文档，整理 OpenProse 与 Lobster 在多智能体准备、确定性执行和审批恢复上的分工，帮助中文团队判断什么时候该用 /prose，什么时候该转成工作流运行时。","/docs/manual/openprose-and-lobster-boundaries",[1079,1080,717,931,659],"openprose","lobster",{"title":1082,"description":1083,"path":1084,"category":758,"updatedAt":1085,"sourceType":589,"tags":1086},"平台支持总览","OpenClaw 支持的操作系统和部署平台，包括 Gateway、桌面应用和移动节点。","/docs/manual/platforms-overview","2026-06-06",[1087,816,1088,1089,1090,1091,1092],"platforms","ios","android","windows","linux","install",{"title":1094,"description":1095,"path":1096,"category":769,"updatedAt":681,"sourceType":589,"tags":1097},"插件托管 hooks 与扩展能力边界","基于最新官方 Plugins 与 Hooks 文档，整理插件托管 hooks 的工作方式、显示位置、启停边界，以及为什么它和独立 hook pack 不是同一种治理对象。","/docs/manual/plugin-managed-hooks",[716,718,660,879,1098],"governance",{"title":1100,"description":1101,"path":1102,"category":769,"updatedAt":681,"sourceType":589,"tags":1103},"插件清单与配置校验","基于最新官方文档，解释 openclaw.plugin.json 的必填字段、校验规则，以及为什么插件清单会直接影响配置是否可通过。","/docs/manual/plugin-manifest",[716,1104,1105,1106,625],"manifest","schema","validation",{"title":1108,"description":1109,"path":1110,"category":769,"updatedAt":681,"sourceType":589,"tags":1111},"插件包与频道目录元信息","根据最新官方插件文档，解释 package packs、插件 id 生成规则、openclaw.channel 元信息，以及为什么这些字段会影响安装与引导体验。","/docs/manual/plugin-package-packs",[716,1112,613,1113,879],"package-packs","metadata",{"title":1115,"description":1116,"path":1117,"category":769,"updatedAt":724,"sourceType":589,"tags":1118},"OpenClaw 插件系统怎么用","基于官方插件与 CLI 文档，解释插件和 Skills、Tools 的边界，说明安装、启用、更新与风险控制的基本方法。","/docs/manual/plugins-overview",[716,879,626,614,790],{"title":1120,"description":1121,"path":1122,"category":769,"updatedAt":724,"sourceType":589,"tags":1123},"模型提供商与故障转移","基于官方 providers 文档，整理 OpenClaw 常见 provider、默认模型写法、fallback 思路和长期运行时的配置重点。","/docs/manual/providers-and-fallback",[798,732,1124,1125,994],"fallback","openrouter",{"title":1127,"description":1128,"path":1129,"category":758,"updatedAt":759,"sourceType":589,"tags":1130},"Queue 系统与消息转向","理解 OpenClaw 的 Queue 系统、消息转向模式和并发控制机制。","/docs/manual/queue-system",[1131,1132,1133,984],"queue","steering","concurrency",{"title":1135,"description":1136,"path":1137,"category":769,"updatedAt":785,"sourceType":589,"tags":1138},"用 SearXNG 给 OpenClaw 配自托管 web_search","基于最新官方 SearXNG Search 文档，整理 OpenClaw 如何接入自托管 SearXNG 作为 web_search provider，以及生产环境里最该注意哪些边界。","/docs/manual/searxng-search-provider",[1139,1140,614,1026,709],"searxng","web-search",{"title":1142,"description":1143,"path":1144,"category":769,"updatedAt":673,"sourceType":770,"tags":1145},"Session 与配对机制","理解 OpenClaw 如何通过配对、allowFrom、群组提及规则和 session 隔离来识别用户并保护上下文边界。","/docs/manual/session-and-pairing",[826,965,613,593],{"title":1147,"description":1148,"path":1149,"category":831,"updatedAt":832,"sourceType":589,"tags":1150},"session memory search 什么时候值得开，什么时候先别开","基于最新官方 Memory 与 memory CLI 文档，整理 OpenClaw 的 session memory search、异步索引刷新、delta threshold 和 embedding cache 各自适合什么场景，帮助团队判断什么时候该扩到会话日志检索。","/docs/manual/session-memory-search-and-index-refresh",[615,764,1027,1151,758],"cache",{"title":1153,"description":1154,"path":1155,"category":769,"updatedAt":673,"sourceType":589,"tags":1156},"Signal 渠道接入重点","Signal 为什么更强调 dedicated number、signal-cli 和 pairing，长期运行时最容易踩哪些坑。","/docs/manual/signal-channel",[613,1157,1158,965,997],"signal","signal-cli",{"title":1160,"description":1161,"path":1162,"category":769,"updatedAt":681,"sourceType":589,"tags":1163},"Signal 群组与 daemon 模式怎么配","基于最新官方 Signal 文档，整理 Signal 在 OpenClaw 里的群组隔离、外部 daemon 模式、多账号和 config writes 边界。","/docs/manual/signal-groups-and-daemon-mode",[1157,825,675,1164,613],"multi-account",{"title":1166,"description":1167,"path":1168,"category":769,"updatedAt":595,"sourceType":589,"tags":1169},"Skills 配置与热重载","理解 OpenClaw 的 skills 配置项、allowBundled、extraDirs、watch、entries.enabled 和运行时环境注入边界。","/docs/manual/skills-configuration",[626,1170,1171,1172,1173],"config","allowBundled","watch","env",{"title":1175,"description":1176,"path":1177,"category":769,"updatedAt":1178,"sourceType":589,"tags":1179},"Skills 系统怎么工作","理解 OpenClaw Skills 的三层来源、加载流程、ClawHub 风险，以及为什么不应该一次安装过多技能。","/docs/manual/skills-system","2026-03-17",[626,860,614,594],{"title":1181,"description":1182,"path":1183,"category":758,"updatedAt":759,"sourceType":589,"tags":1184},"流式输出与分块机制","理解 OpenClaw 的两层流式输出机制：块流式（实时发送）和预览流式（实时预览），以及如何配置。","/docs/manual/streaming-and-chunking",[1185,1186,1187,1188,613],"streaming","chunking","block","preview",{"title":1190,"description":1191,"path":1192,"category":769,"updatedAt":927,"sourceType":589,"tags":1193},"系统提示词、上下文与压缩","基于官方 system prompt、context、compaction 与 session pruning 文档，解释 OpenClaw 一次运行到底会把什么发给模型，以及上下文为什么会变满。","/docs/manual/system-prompt-context-and-compaction",[1194,1195,1196,1197,764],"system-prompt","context","compaction","pruning",{"title":1199,"description":1200,"path":1201,"category":769,"updatedAt":724,"sourceType":589,"tags":1202},"Telegram 与 WhatsApp 接入重点","两个最常见的入门渠道该怎么选、各自依赖什么认证方式，以及群聊和私聊里最容易踩的坑。","/docs/manual/telegram-and-whatsapp",[613,852,853,965,1203],"bot",{"title":1205,"description":1206,"path":1207,"category":769,"updatedAt":724,"sourceType":589,"tags":1208},"Telegram 和 Discord 作为审批入口时该怎么收边界","基于最新官方 Exec Approvals 文档，解释 Telegram 与 Discord 作为 exec approval 客户端时分别扮演什么角色、哪些配置值得先看，以及为什么它们适合作为受控审批入口而不是普通开放群聊。","/docs/manual/telegram-discord-approval-clients",[852,854,931,613,929,594],{"title":1210,"description":1211,"path":1212,"category":769,"updatedAt":673,"sourceType":589,"tags":1213},"OpenClaw 的 Tools 与扩展能力概览","从中文用户角度理解 OpenClaw 的工具层、技能层和自动化扩展边界，知道它为什么不只是聊天助手。","/docs/manual/tools-overview",[614,626,718,660],{"title":1215,"description":1216,"path":1217,"category":769,"updatedAt":724,"sourceType":589,"tags":1218},"vLLM 本地模型 Provider 怎么接","基于最新官方 vLLM provider 文档，整理 OpenClaw 如何接入 vLLM、本地自动发现和手动模型声明各自适合什么场景。","/docs/manual/vllm-local-model-provider",[1219,1220,798,709,1221],"vllm","local-models","inference",{"title":1223,"description":1224,"path":1225,"category":769,"updatedAt":673,"sourceType":589,"tags":1226},"语音唤醒与 Talk Mode","理解 OpenClaw 的 voice wake 是怎么和 Gateway、nodes、客户端一起工作的，以及什么时候值得启用它。","/docs/manual/voice-wake-and-talk-mode",[900,1227,1228,779,841],"wake-word","talk-mode",{"title":1230,"description":1231,"path":1232,"category":769,"updatedAt":724,"sourceType":589,"tags":1233},"WebChat 与 message CLI","理解 OpenClaw 除聊天渠道外的两类直接交互入口：Gateway WebSocket 上的 WebChat 和统一的 openclaw message 命令。","/docs/manual/webchat-and-message-cli",[739,1234,790,285,613],"message",{"title":1236,"description":1237,"path":1238,"category":769,"updatedAt":1239,"sourceType":589,"tags":1240},"WebChat、API 和控制面入口的边界怎么分","基于最新官方 WebChat、Session 和 API 文档，解释 WebChat 为什么更像会话 UI、HTTP API 为什么更像结构化管理面，以及 Dashboard 为什么仍然属于高权限控制面。","/docs/manual/webchat-api-and-control-surface-boundaries","2026-03-26",[739,1241,668,285,937],"api",{"title":1243,"description":1244,"path":1245,"category":769,"updatedAt":681,"sourceType":589,"tags":1246},"WebChat 的会话与只读边界","基于最新官方 WebChat 文档，整理 WebChat 如何共享 Gateway 会话、chat.inject 和 abort partial 是什么，以及 Gateway 不可达时为什么会进入只读模式。","/docs/manual/webchat-session-and-readonly-mode",[739,764,1247,1248,1249],"websocket","readonly","chat",{"title":1251,"description":1252,"path":1253,"category":769,"updatedAt":724,"sourceType":589,"tags":1254},"用 Webhooks 接外部系统","基于最新官方 Webhooks 文档，整理 OpenClaw 如何通过 /hooks 接收外部事件，重点解释 wake、agent、映射、投递和安全边界。","/docs/manual/webhooks-external-triggers",[1255,718,660,1256,594],"webhooks","integrations",{"title":1258,"description":1259,"path":1260,"category":579,"updatedAt":804,"sourceType":589,"tags":1261},"Exec approvals 转发到聊天渠道该怎么设计","基于最新官方 approvals 文档，解释 OpenClaw 如何把 exec approval 请求转发到聊天渠道、/approve 命令怎么工作，以及为什么它适合远程值班但不适合无限扩散批准权。","/docs/operations/chat-approval-forwarding",[931,929,1249,1262,633],"forwarding",{"title":1264,"description":1265,"path":1266,"category":579,"updatedAt":681,"sourceType":589,"tags":1267},"配置热重载与 include 合并怎么用","基于最新官方 Configuration 文档，整理 OpenClaw 的 config hot reload、reload mode、include 深度合并和哪些改动需要重启。","/docs/operations/config-hot-reload-and-includes",[625,1268,1269,1270,1271],"hot-reload","includes","merge","restart",{"title":1273,"description":1274,"path":1275,"category":579,"updatedAt":681,"sourceType":589,"tags":1276},"远程打开 Control UI 的正确方式","基于最新官方 Control UI、Dashboard 和 Tailscale 文档，整理远程访问 Control UI 时最稳的路径、常见 1008 报错原因，以及 allowedOrigins 等关键边界。","/docs/operations/control-ui-remote-access",[886,668,1277,1278,1279],"remote-access","tailscale","allowedOrigins",{"title":1281,"description":1282,"path":1283,"category":579,"updatedAt":804,"sourceType":589,"tags":1284},"Cron 的 retention 和 run log pruning 怎么工作","基于最新官方 Cron Jobs 与配置文档，解释 isolated cron run 的 sessionRetention、runLog 裁剪、transcript archive 和高频调度下的磁盘足迹，避免把 cron 当成无限保留的后台队列。","/docs/operations/cron-retention-and-run-log-pruning",[788,1285,1197,1286,633],"retention","runlog",{"title":1288,"description":1289,"path":1290,"category":579,"updatedAt":681,"sourceType":589,"tags":1291},"定时任务与心跳怎么选","根据最新官方自动化文档，解释 Heartbeat、Cron main、Cron isolated 三种机制分别适合什么场景，以及它们在精度、上下文和成本上的差异。","/docs/operations/cron-vs-heartbeat",[660,788,1292,1293,633],"heartbeat","scheduling",{"title":1295,"description":1296,"path":1297,"category":579,"updatedAt":804,"sourceType":589,"tags":1298},"Dashboard 管理面怎么更稳地开放","基于最新官方 Dashboard、remote access 和 pairing 文档，整理管理员面该如何开放、保存 token、限制入口和处理 unauthorized/1008，避免把 Control UI 变成公开风险面。","/docs/operations/dashboard-admin-surface-hardening",[668,886,683,594,1299],"admin",{"title":1301,"description":1302,"path":1303,"category":579,"updatedAt":1239,"sourceType":589,"tags":1304},"Dashboard 遇到 unauthorized、1008 和 AUTH_TOKEN_MISMATCH 时怎么恢复","基于最新官方 Dashboard 文档，整理 OpenClaw 在 Dashboard 认证失败时更稳的恢复顺序，尤其是 AUTH_TOKEN_MISMATCH、trusted retry、SecretRef token 和远程实例混淆这几类问题。","/docs/operations/dashboard-auth-mismatch-recovery",[668,593,1305,1306,633],"unauthorized","1008",{"title":1308,"description":1309,"path":1310,"category":579,"updatedAt":822,"sourceType":589,"tags":1311},"设备 pairing、fresh token 和 revoke 应该怎么做日常运维","基于最新官方 Pairing 与 Devices CLI 文档，解释 openclaw devices list、approve、rotate、revoke 和 fresh token 的真实边界，以及为什么设备授权不该被当成一次性静态批准。","/docs/operations/device-pairing-token-lifecycle",[966,965,906,1312,633],"revoke",{"title":1314,"description":1315,"path":1316,"category":579,"updatedAt":822,"sourceType":589,"tags":1317},"doctor 的备份、unknown keys 清理和 --fix 该怎么理解","基于最新官方 Doctor 文档，解释 openclaw doctor 在修复 stale config、unknown keys 和 legacy 状态时的备份与收口方式，帮助团队区分安全修复和强制覆盖。","/docs/operations/doctor-fix-backups-and-unknown-keys",[1318,1319,1320,1170,1321],"doctor","repair","backups","unknown-keys",{"title":1323,"description":1324,"path":1325,"category":579,"updatedAt":673,"sourceType":589,"tags":1326},"Gateway 运维与日常检查","围绕状态检查、访问方式、日志与升级窗口，建立 OpenClaw Gateway 的日常运维习惯。","/docs/operations/gateway-operations",[285,633,1327,1034],"status",{"title":1329,"description":1330,"path":1331,"category":579,"updatedAt":681,"sourceType":589,"tags":1332},"Gmail Pub/Sub 接入 OpenClaw","根据最新官方自动化文档，整理 Gmail watch、Google Pub/Sub、Webhook 映射和 Tailscale Funnel 的接入顺序，帮助你把 Gmail 事件稳定送进 OpenClaw。","/docs/operations/gmail-pubsub",[1333,1334,1255,660,1278],"gmail","pubsub",{"title":1336,"description":1337,"path":1338,"category":579,"updatedAt":620,"sourceType":589,"tags":1339},"长期运行时，如何管理会话、记忆与压缩","把 session、memory、compaction 和重置策略放到同一条治理链里，帮助长期运行的 OpenClaw 环境建立更稳定的上下文边界。","/docs/operations/long-session-governance",[764,615,1196,1098,633],{"title":1341,"description":1342,"path":1343,"category":579,"updatedAt":724,"sourceType":589,"tags":1344},"模型选型与成本控制","从主力模型、fallback、国内 provider 和低价值任务分流四个角度理解 OpenClaw 的模型配置策略与成本控制方法。","/docs/operations/model-strategy-and-cost",[732,1345,798,1124,1346,1347,1348],"cost","qwen","qianfan","kimi",{"title":1350,"description":1351,"path":1352,"category":579,"updatedAt":681,"sourceType":589,"tags":1353},"用 models status 做模型健康检查","基于最新官方 Models CLI 与 Auth Monitoring 文档，整理 openclaw models status 在日常运维里的正确用法、退出码含义和适合接入监控的检查方式。","/docs/operations/models-status-and-health-checks",[732,1354,593,1070,1355],"health-check","monitoring",{"title":1357,"description":1358,"path":1359,"category":579,"updatedAt":673,"sourceType":589,"tags":1360},"多 Gateway 与隔离运行","当一台机器上需要运行多个 OpenClaw 实例时，如何用 profile、独立端口和独立状态目录避免冲突。","/docs/operations/multiple-gateways",[285,1361,1362,1363,633],"profile","multi-instance","isolation",{"title":1365,"description":1366,"path":1367,"category":579,"updatedAt":927,"sourceType":589,"tags":1368},"网络模型、发现与配对","基于官方网络中心、配对和 Gateway 拥有的配对文档，梳理 localhost、tailnet、发现、身份和审批之间的关系。","/docs/operations/network-and-pairing",[1369,965,1370,1371,1372],"network","identity","tailnet","mdns",{"title":540,"description":1374,"path":539,"category":579,"updatedAt":724,"sourceType":589,"tags":1375},"了解使用 OpenClaw 时的安全最佳实践，包括密码管理、权限控制和日志监控。",[594,1376,1377],"best-practices","guide",{"title":1379,"description":1380,"path":1381,"category":579,"updatedAt":804,"sourceType":589,"tags":1382},"Compaction 前的 memory flush 在保护什么","基于最新官方 Memory、Compaction 和会话管理文档，解释 pre-compaction memory flush 的触发时机、NO_REPLY 机制、软阈值公式，以及为什么它是长期使用体验里的关键缓冲层。","/docs/operations/pre-compaction-memory-flush",[615,1196,1383,1384,633],"flush","NO_REPLY",{"title":1386,"description":1387,"path":1388,"category":1389,"updatedAt":724,"sourceType":589,"tags":1390},"如何持续跟踪 OpenClaw 更新","建立一套低成本的更新跟踪方法，并把官方 release 和文档变化转化成真正可执行的中文维护动作。","/docs/operations/release-tracking","更新",[1391,1392,1393,1394],"release","changelog","updates","maintenance",{"title":546,"description":1396,"path":545,"category":579,"updatedAt":724,"sourceType":589,"tags":1397},"把 OpenClaw 放到远程主机长期运行时，如何在 SSH、tailnet、Tailscale Serve 和直接 ws/wss 之间做选择。",[683,1398,1278,285,633],"ssh",{"title":1400,"description":1401,"path":1402,"category":579,"updatedAt":673,"sourceType":589,"tags":1403},"Remote Operators 与多设备协作","当 Gateway 跑在远程主机、操作入口分散在多台设备上时，如何理解 operator、node 和长期在线实例的协作边界。","/docs/operations/remote-operators-and-nodes",[683,1404,779,1278,1398,966],"operators",{"title":534,"description":1406,"path":533,"category":579,"updatedAt":673,"sourceType":589,"tags":1407},"从 Gateway auth、allowlist、Control UI 暴露方式和 Tailscale/SSH 接入策略理解 OpenClaw 的基础安全边界。",[594,593,1278,668],{"title":1409,"description":1410,"path":1411,"category":579,"updatedAt":724,"sourceType":589,"tags":1412},"security audit、--deep 和 --fix 该怎么配合","基于最新官方安全文档，解释 openclaw security audit、--deep 与 --fix 各自适合什么阶段，哪些问题适合自动修复，哪些仍应人工复核。","/docs/operations/security-audit-fix-and-review",[594,1413,1414,1415,633],"audit","hardening","fix",{"title":1417,"description":1418,"path":1419,"category":579,"updatedAt":804,"sourceType":589,"tags":1420},"sessions cleanup 和 session maintenance 应该怎么配合","基于最新官方 sessions CLI 文档，解释 openclaw sessions cleanup 的作用范围、dry-run/enforce 语义、active-key 保护，以及它和 cron maintenance 不是同一层清理。","/docs/operations/sessions-cleanup-and-maintenance",[764,1421,1394,1422,633],"cleanup","transcripts",{"title":1424,"description":1425,"path":1426,"category":579,"updatedAt":822,"sourceType":589,"tags":1427},"shared inbox 的运营边界和信任模型","基于最新官方 Security、Session 和 Groups 文档，解释 OpenClaw 对 shared inbox 的默认安全假设、适合的协作硬化方式，以及为什么真正的互不信任多租户场景更应该拆成独立 gateway。","/docs/operations/shared-inbox-trust-boundaries",[594,1428,1429,285,633],"shared-inbox","trust-model",{"title":1431,"description":1432,"path":1433,"category":579,"updatedAt":927,"sourceType":589,"tags":1434},"Tailscale Serve / Funnel 怎么选","基于官方 Tailscale 文档，解释 serve、funnel、tailnet 绑定和 allowTailscale 的差异，以及更稳的使用边界。","/docs/operations/tailscale-serve-and-funnel",[1278,1435,1436,285,593],"serve","funnel",{"title":1438,"description":1439,"path":1440,"category":579,"updatedAt":673,"sourceType":589,"tags":1441},"团队频道里的 Session 隔离策略","当 OpenClaw 进入 Discord、Slack 等多人频道后，如何把频道、线程、私聊和长期记忆分开，避免上下文污染。","/docs/operations/team-channel-session-strategy",[826,854,921,623,1442,633],"group-chat",{"title":5,"description":581,"path":585,"category":579,"updatedAt":595,"sourceType":589,"tags":1444},[20,592,593,285,594],{"title":1446,"description":1447,"path":1448,"category":579,"updatedAt":681,"sourceType":589,"tags":1449},"Trusted Proxy 和 Tailscale Serve 怎么选","基于最新官方安全与 trusted proxy 文档，解释 OpenClaw 在 trusted-proxy、token/password 和 Tailscale Serve 之间各自适合什么场景。","/docs/operations/trusted-proxy-vs-tailscale-serve",[20,1278,592,593,285,594],{"title":1451,"description":1452,"path":1453,"category":579,"updatedAt":724,"sourceType":589,"tags":1454},"stable、beta、dev 更新通道该怎么选","基于最新官方 update CLI 与 Updating 文档，解释 OpenClaw 的 stable、beta、dev 三条更新轨道、auto-updater 行为和更适合的长期 rollout 顺序。","/docs/operations/update-channels-and-safe-rollout",[1455,613,1456,1457,1458,1459],"update","stable","beta","dev","rollout",{"title":1461,"description":1462,"path":1463,"category":1464,"updatedAt":832,"sourceType":589,"tags":1465},"Anthropic context1m 的 429 和 fallback 应该怎么处理","基于最新官方 Gateway Troubleshooting 与 Model Failover 文档，解释 Anthropic 长上下文 429 为什么常只在长 session 里出现、什么时候该关掉 context1m，以及怎样用 fallback 把这类拒绝变成可恢复事件。","/docs/reference/anthropic-context1m-429-and-fallback","参考",[1466,1467,1468,1469,1470],"anthropic","429","context1m","failover","reference",{"title":1472,"description":1473,"path":1474,"category":1464,"updatedAt":673,"sourceType":589,"tags":1475},"API 与参考资料阅读入口","说明 OpenClaw 的参考资料应如何阅读，以及中文用户在查 CLI、配置、诊断和模块说明时该怎么找信息。","/docs/reference/api-reference-overview",[1470,790,1170,1476],"diagnostics",{"title":1478,"description":1479,"path":1480,"category":1464,"updatedAt":724,"sourceType":589,"tags":1481},"approvals CLI、网关与节点 allowlist 怎么管理","基于最新官方 approvals CLI 与 Exec Approvals 文档，解释 openclaw approvals 在本机、Gateway 和 Node 上分别管理什么，以及 per-agent allowlist 最值得先守住哪些边界。","/docs/reference/approvals-cli-and-allowlist",[931,1051,929,285,1482,1470],"node",{"title":1484,"description":1485,"path":1486,"category":1464,"updatedAt":832,"sourceType":589,"tags":1487},"认证配置文件怎么轮转，为什么 session 会“粘住”同一套凭据","基于最新官方 Model Failover 文档，解释 OpenClaw 在同一 provider 内如何轮转 auth profiles、什么情况下会进入 cooldown，以及为什么同一个 session 往往会持续使用同一套凭据。","/docs/reference/auth-profile-rotation-and-session-pinning",[593,1073,1469,764,1470],{"title":1489,"description":1490,"path":1491,"category":1464,"updatedAt":832,"sourceType":589,"tags":1492},"setup code、bootstrapToken 和 /pair pending 应该怎么一起看","基于最新官方 Pairing 文档，解释 Telegram 首次设备接入时 setup code 里到底装了什么、bootstrapToken 只负责哪一步，以及为什么最后仍然要回到 /pair pending 做人工批准。","/docs/reference/bootstrap-code-and-pair-pending",[965,1493,852,966,1470],"bootstrapToken",{"title":1495,"description":1496,"path":1497,"category":1470,"updatedAt":759,"sourceType":589,"tags":1498},"引导文件模板系统","AGENTS.md、SOUL.md、BOOTSTRAP.md 等引导文件的用途、写法和最佳实践。","/docs/reference/bootstrap-templates",[1499,763,808,772,1370,762],"templates",{"title":1501,"description":1502,"path":1503,"category":1464,"updatedAt":822,"sourceType":589,"tags":1504},"频道 pairing CLI 和 account scope 应该怎么一起看","基于最新官方 Pairing 文档，解释 openclaw pairing 的 list、approve、clear、--account 与 --notify 分别影响什么，以及多账号渠道下为什么不能只看一个默认 allowFrom 文件。","/docs/reference/channel-pairing-cli-and-account-scope",[965,1505,613,1506,1299],"allowFrom","account",{"title":1508,"description":1509,"path":1510,"category":1464,"updatedAt":927,"sourceType":589,"tags":1511},"CLI 命令参考","OpenClaw 命令行工具完整参考，包含所有命令和选项说明。","/docs/reference/cli-reference",[790,1470,1512,1513],"commands","terminal",{"title":1515,"description":1516,"path":1517,"category":1464,"updatedAt":832,"sourceType":589,"tags":1518},"Cloudflare AI Gateway 的双层鉴权头应该怎么配","基于最新官方 Cloudflare AI Gateway 文档，解释 provider API key 和 cf-aig-authorization 为什么是两层不同凭据，以及 daemon 场景里最常见的缺失点。","/docs/reference/cloudflare-aig-dual-auth-headers",[1519,1520,593,798,1470],"cloudflare-ai-gateway","headers",{"title":1522,"description":1523,"path":1524,"category":1525,"updatedAt":724,"sourceType":877,"tags":1526},"社区支持","汇总 OpenClaw 的官方社区入口、反馈方式、提问建议和中文用户更适合的参与路径。","/docs/reference/community","社区",[877,1527,1528,1529],"github","issues","feedback",{"title":1531,"description":1532,"path":1533,"category":1464,"updatedAt":927,"sourceType":589,"tags":1534},"配置参考","OpenClaw 完整配置项参考文档，包含所有可配置选项的详细说明。","/docs/reference/configuration-reference",[625,1470,1535,1536],"settings","options",{"title":1538,"description":1539,"path":1540,"category":1464,"updatedAt":681,"sourceType":589,"tags":1541},"Control UI 设备配对与浏览器授权","基于最新官方 Control UI 与 Pairing 文档，解释为什么远程浏览器首次连接需要设备配对、设备身份如何记住，以及什么时候需要重新批准。","/docs/reference/control-ui-device-pairing",[886,965,966,907,1299],{"title":1543,"description":1544,"path":1545,"category":1464,"updatedAt":832,"sourceType":589,"tags":1546},"cron run 入队语义和 retry backoff 应该怎么理解","基于最新官方 cron CLI 与 Cron Jobs 文档，解释 openclaw cron run 为什么先返回 enqueued、何时该去看 runs，以及 recurring job 连续失败后的退避节奏。","/docs/reference/cron-run-queue-and-retry-backoff",[788,1045,1547,1131,1470],"scheduler",{"title":1549,"description":1550,"path":1551,"category":1464,"updatedAt":1239,"sourceType":589,"tags":1552},"Dashboard 的 SecretRef token、sessionStorage 和非 token 化 URL 应该怎么理解","基于最新官方 Dashboard 文档，解释 openclaw dashboard 在普通 token、SecretRef token 和远程入口下分别如何引导认证，以及为什么当前浏览器标签页的 sessionStorage 行为很关键。","/docs/reference/dashboard-secretref-and-sessionstorage",[668,906,1553,1554,593],"secretref","sessionStorage",{"title":1556,"description":1557,"path":1558,"category":1559,"updatedAt":927,"sourceType":589,"tags":1560},"调试、运行时覆盖与开发排障","基于官方 debugging 和 FAQ 文档，整理 `/debug`、watch 模式、dev profile 以及排查流式输出异常时最值得先看的入口。","/docs/reference/debugging-and-runtime-overrides","排错",[1561,1562,1563,1318,1034],"debugging","debug","runtime-overrides",{"title":1565,"description":1566,"path":1567,"category":1464,"updatedAt":804,"sourceType":589,"tags":1568},"Diagnostics flags 和定向日志应该怎么用","基于最新官方 Diagnostics Flags 与 Logging 文档，解释 OpenClaw 如何用 diagnostics.flags 和 OPENCLAW_DIAGNOSTICS 打开定向调试日志，以及为什么这比全局 verbose 更适合长期排障。","/docs/reference/diagnostics-flags-and-targeted-logs",[1476,1569,1570,1562,1470],"logging","flags",{"title":1572,"description":1573,"path":1574,"category":1464,"updatedAt":804,"sourceType":589,"tags":1575},"dmScope 和 identityLinks 应该怎么一起用","基于最新官方会话管理文档，解释 OpenClaw 的 dmScope 四种模式、identityLinks 的真实作用，以及为什么多人 DM、跨渠道私聊和多账户环境不能只改一个开关。","/docs/reference/dm-scope-and-identity-links",[826,1576,1577,807,1470],"dmScope","identityLinks",{"title":1579,"description":1580,"path":1581,"category":1464,"updatedAt":804,"sourceType":589,"tags":1582},"doctor 的 repair、force 和 non-interactive 应该怎么选","基于最新官方 Doctor 文档，解释 openclaw doctor 在 interactive、--repair、--force、--yes、--non-interactive 和 --deep 之间各自会做什么，避免把修复模式混成“越猛越好”。","/docs/reference/doctor-repair-modes",[1318,1319,1476,1583,1470],"migrations",{"title":1585,"description":1586,"path":1587,"category":1464,"updatedAt":804,"sourceType":589,"tags":1588},"环境变量从哪里来，优先级怎么排","基于最新官方 Environment Variables 与 Configuration 文档，解释 OpenClaw 会从哪些来源读取环境变量、为什么默认不覆盖已有值，以及 `.env`、config env 和 shell import 之间真正的优先级。","/docs/reference/env-sources-and-precedence",[1173,625,834,1589,1470],"shell",{"title":1591,"description":1592,"path":1593,"category":1464,"updatedAt":724,"sourceType":609,"tags":1594},"如何结合官方文档、GitHub 和中文渠道跟踪 OpenClaw","把官方文档、GitHub Releases、Issues、中文教程站、媒体报道和中文社区解读放到同一套可信度框架里，减少信息滞后和误读。","/docs/reference/external-sources-and-trust-levels",[1595,1391,877,1596,1393],"sources","trust",{"title":1598,"description":1599,"path":1600,"category":1464,"updatedAt":681,"sourceType":589,"tags":1601},"Gateway 命令与 RPC 该怎么用","基于最新官方 CLI Reference 与 Gateway protocol 文档，整理 openclaw gateway 子命令、RPC 调用边界、显式凭据要求，以及为什么它更适合被当成控制面入口而不是随手脚本助手。","/docs/reference/gateway-cli-and-rpc",[285,1602,790,1247,780],"rpc",{"title":1604,"description":1605,"path":1606,"category":1464,"updatedAt":804,"sourceType":589,"tags":1607},"Gateway-owned pairing 和 device pairing 有什么区别","基于最新官方 Pairing 与 Gateway-owned pairing 文档，解释 node.pair.* 这套旧式网关配对和当前 WS device pairing 的真实边界，避免把两套授权机制混成一套。","/docs/reference/gateway-owned-pairing-vs-device-pairing",[965,966,285,779,1470],{"title":1609,"description":1610,"path":1611,"category":1464,"updatedAt":1239,"sourceType":589,"tags":1612},"Gateway 为什么是 session source of truth","基于最新官方 Session 文档，解释 OpenClaw 的 session store、JSONL transcript、token 计数和 UI 查询为什么都应围绕 Gateway 理解，避免把本地浏览器、WebChat 或 operator 设备误当成真实状态源。","/docs/reference/gateway-session-source-of-truth",[826,285,739,668,1470],{"title":1614,"description":1615,"path":1616,"category":1464,"updatedAt":832,"sourceType":589,"tags":1617},"Gateway WebSocket 的 role 和 scope 应该怎么理解","基于最新官方 Gateway Protocol 文档，解释 OpenClaw 的 WebSocket 握手里 role、scopes、client mode 和协议版本各自在声明什么，以及为什么这条连接已经是统一控制面而不只是聊天通道。","/docs/reference/gateway-ws-roles-and-scopes",[285,1247,1618,1619,1470],"protocol","scopes",{"title":1621,"description":1622,"path":1623,"category":1464,"updatedAt":822,"sourceType":589,"tags":1624},"groupPolicy、allowlist 和 mention gating 的顺序应该怎么理解","基于最新官方 Groups、Group Messages 和 Messages 文档，解释 OpenClaw 在群聊里如何按 groupPolicy、群组 allowlist 和 mention gating 三层顺序决定消息是丢弃、只进上下文，还是正式触发回复。","/docs/reference/group-policy-and-mention-gating-order",[825,1625,807,1051,984],"mention",{"title":1627,"description":1628,"path":1629,"category":1464,"updatedAt":832,"sourceType":589,"tags":1630},"HEARTBEAT_OK、可见性控制和 quiet-hours 应该怎么一起看","基于最新官方 Heartbeat 与 Automation Troubleshooting 文档，解释 HEARTBEAT_OK 的 ack 语义、alerts-disabled 和 dm-blocked 等可见性控制，以及 quiet-hours 为什么不是故障。","/docs/reference/heartbeat-ack-and-visibility-controls",[1292,1631,1632,1633,1470],"visibility","activeHours","alerts",{"title":1635,"description":1636,"path":1637,"category":1464,"updatedAt":822,"sourceType":589,"tags":1638},"HTTP API、Gateway WebSocket 和 SDK 应该怎么分工","基于最新官方 API 与 Web 文档，解释 OpenClaw 里 HTTP API、Gateway WebSocket 和 SDK 各自适合什么场景，帮助团队判断当前到底应该走管理接口、实时会话层还是语言 SDK。","/docs/reference/http-api-vs-gateway-websocket-vs-sdk",[1241,1247,1639,285,1470],"sdk",{"title":1641,"description":1642,"path":1643,"category":1464,"updatedAt":822,"sourceType":589,"tags":1644},"include 合并时，数组和 sibling override 到底怎么生效","基于最新官方 Configuration 文档，解释 OpenClaw 在 $include 合并时数组、对象和 sibling keys 的真实处理顺序，帮助团队避免把 include 当成“总是深合并”的黑盒。","/docs/reference/include-merge-arrays-and-sibling-overrides",[625,1645,1270,1646,1470],"include","arrays",{"title":1648,"description":1649,"path":1650,"category":1464,"updatedAt":804,"sourceType":589,"tags":1651},"Lobster 的调用、审批和 resume token","基于最新官方 Lobster 文档，解释 OpenClaw 里如何用 openclaw.invoke 触发确定性工作流、何时进入 needs_approval，以及 resume token 在恢复流程里扮演什么角色。","/docs/reference/lobster-invoke-and-resume",[1080,1652,931,659,1470],"invoke",{"title":1654,"description":1655,"path":1656,"category":1464,"updatedAt":832,"sourceType":589,"tags":1657},"记忆检索里的 hybrid search、重排和时间衰减到底在做什么","基于最新官方 Memory 文档，解释 OpenClaw 的 memory_search 为什么不只是向量检索，以及 hybrid search、结果合并、MMR 重排和 temporal decay 各自在修正什么问题。","/docs/reference/memory-hybrid-search-and-ranking-pipeline",[615,1658,1659,1660,1661,1470],"hybrid-search","ranking","mmr","retrieval",{"title":1663,"description":1664,"path":1665,"category":1464,"updatedAt":724,"sourceType":589,"tags":1666},"models status --probe 和 auth profiles 应该怎么看","基于最新官方 Models CLI 文档，解释 openclaw models status --probe、--probe-provider 与认证 profile 的关系，帮助团队区分“配置看起来对”和“当前真的能连通”。","/docs/reference/models-status-probe-and-auth-profiles",[732,1667,593,798,1470],"probe",{"title":1669,"description":1670,"path":1671,"category":1464,"updatedAt":595,"sourceType":589,"tags":1672},"配对审批与设备授权管理","从管理员视角理解 OpenClaw 的 DM pairing、设备 pairing、allowFrom 文件和审批命令，避免把授权边界搞乱。","/docs/reference/pairing-admin",[965,966,1505,1673,1299],"credentials",{"title":1675,"description":1676,"path":1677,"category":1464,"updatedAt":724,"sourceType":589,"tags":1678},"插件安装 spec、--pin 和 update tracking 应该怎么理解","基于最新官方 plugins CLI 文档，解释 ClawHub first、npm-safe spec、--pin、prerelease opt-in 和 plugins.installs 的跟踪逻辑，帮助团队判断插件后续会按什么规则更新。","/docs/reference/plugins-install-specs-and-update-tracking",[716,860,1679,1680,1393,1470],"npm","pin",{"title":1682,"description":1683,"path":1684,"category":1559,"updatedAt":681,"sourceType":589,"tags":1685},"原始流日志怎么抓","基于最新官方 Debugging 文档，整理 OpenClaw 的 raw stream、pi-mono raw chunk 日志分别该在什么场景开启，以及如何避免把调试日志变成隐私风险。","/docs/reference/raw-stream-debugging",[1561,1686,1034,798,997],"raw-stream",{"title":1688,"description":1689,"path":1690,"category":1464,"updatedAt":832,"sourceType":589,"tags":1691},"remote auth fallback 和 tlsFingerprint 应该什么时候用","基于最新官方 Remote Access 文档，解释 gateway.remote 这套远程连接参数什么时候只是兜底、什么时候会 fail closed，以及 tlsFingerprint 在 wss 场景里真正保护什么。","/docs/reference/remote-auth-fallback-and-tls-fingerprint",[683,1692,593,285,1470],"tlsFingerprint",{"title":1694,"description":1695,"path":1696,"category":1464,"updatedAt":832,"sourceType":589,"tags":1697},"回复机器人消息也算 mention 吗，pending history 又什么时候会进上下文","基于最新官方 Groups 与 Group Messages 文档，解释 OpenClaw 在群聊里怎样把 reply metadata 当成隐式 mention，以及未触发回复的群消息何时只进入 pending history、何时会被彻底丢弃。","/docs/reference/reply-mention-and-pending-history",[825,1698,1699,1700,1470],"mentions","pending-history","reply",{"title":1702,"description":1703,"path":1704,"category":1464,"updatedAt":804,"sourceType":589,"tags":1705},"SecretRefs 和运行时快照应该怎么理解","基于最新官方 Secrets Management 文档，解释 env/file/exec secret refs 的解析时机、活动面、失败模式和热重载语义，避免把密钥管理误解成“请求时临时去取”。","/docs/reference/secret-refs-and-runtime-snapshot",[1706,1707,761,798,1470],"secrets","secretrefs",{"title":1709,"description":1710,"path":1711,"category":1464,"updatedAt":822,"sourceType":589,"tags":1712},"secure DM mode 和 owner pinning 应该怎么一起理解","基于最新官方 Session 与 Security 文档，解释 OpenClaw 的 secure DM mode、owner pinning、pairing / allowlist / open 三类 DM 入口，以及什么时候该从连续主会话切到隔离模式。","/docs/reference/secure-dm-mode-and-owner-pinning",[826,594,1576,965,1051],{"title":1714,"description":1715,"path":1716,"category":1464,"updatedAt":1717,"sourceType":589,"tags":1718},"session JSONL、compaction entry 和 branch summary 应该怎么理解","基于最新官方 Session Management Deep Dive 文档，解释 OpenClaw 的 session JSONL 结构、compaction entry、branch summary 和 store counters 分别在回答什么问题，避免把 transcript 文件当成一团无结构日志。","/docs/reference/session-jsonl-and-compaction-entries","2026-04-01",[826,1719,1720,1196,1470],"transcript","jsonl",{"title":1722,"description":1723,"path":1724,"category":1464,"updatedAt":1717,"sourceType":589,"tags":1725},"openclaw sessions 的 store scope 和巡检方式","基于最新官方 sessions CLI 文档，解释 openclaw sessions 在默认 agent、单 agent、all-agents 和显式 store 路径下分别在看什么，以及长期运维里为什么值得把它当作 session store 巡检入口。","/docs/reference/sessions-cli-store-scope-and-audit",[764,790,1726,1413,633],"store",{"title":1728,"description":1729,"path":1730,"category":1464,"updatedAt":832,"sourceType":589,"tags":1731},"哪些配置会被官方当成 shared-user ingress 信号","基于最新官方 security audit 文档，解释 OpenClaw 为什么会把开放 DM、群目标和 wildcard sender 规则识别成 shared-user ingress 信号，以及这些提醒真正想让你检查什么。","/docs/reference/shared-user-ingress-signals",[594,1428,1413,1732,1470],"ingress",{"title":1734,"description":1735,"path":1736,"category":1464,"updatedAt":681,"sourceType":589,"tags":1737},"status、health 和 logs 该怎么分工","基于最新官方 CLI reference，整理 openclaw status、health、logs 三组命令各自应该回答什么问题，以及值班和排障时更稳的使用顺序。","/docs/reference/status-health-and-logs",[790,1327,1738,1034,1739],"health","troubleshooting",{"title":1741,"description":1742,"path":1743,"category":1464,"updatedAt":1717,"sourceType":589,"tags":1744},"对话记录清理（provider fixups）到底改了什么，不改什么","基于最新官方 Transcript Hygiene 文档，解释 OpenClaw 在运行前对 transcript 做的 provider-specific fixups、图片清理、tool 调用配对修复和思考签名清理分别解决什么问题，以及为什么它不会重写磁盘 JSONL。","/docs/reference/transcript-hygiene-and-provider-fixups",[1719,1745,798,1746,1470],"hygiene","tool-calls",{"title":552,"description":1748,"path":551,"category":1559,"updatedAt":673,"sourceType":589,"tags":1749},"把 OpenClaw 常见问题按环境、入口、配置、认证和运行状态拆开，建立更高效的排查顺序。",[1739,1318,1327,1034],{"title":1751,"description":1752,"path":1753,"category":1464,"updatedAt":804,"sourceType":589,"tags":1754},"WebChat 的 history、inject 和展示边界","基于最新官方 WebChat 文档，整理 chat.history 的截断/占位规则、chat.inject 的真实用途，以及为什么 WebChat 看见的 transcript 不是原始 JSONL 的一比一镜像。","/docs/reference/webchat-history-and-inject-boundaries",[739,1755,1756,1719,1470],"history","inject",{"title":1758,"description":1759,"path":1760,"category":1761,"updatedAt":724,"sourceType":589,"tags":1762},"国内云部署思路","面向中文团队整理 OpenClaw 在国内或面向国内网络环境部署时最该先判断的三件事：入口生态、模型端点和长期在线后的运维边界。","/docs/setup/china-cloud-deployment","安装",[1763,1764,1765,943,1346,1347],"china","cloud","deployment",{"title":1767,"description":1768,"path":1769,"category":1761,"updatedAt":673,"sourceType":589,"tags":1770},"部署方式怎么选","从本地安装、Docker、国内云模板和海外一键部署四类路径理解 OpenClaw 的部署选择，而不是只追求“最快装上”。","/docs/setup/deployment-options",[1765,684,1771,1764,1772],"docker","wsl2",{"title":1774,"description":1775,"path":1776,"category":1761,"updatedAt":1178,"sourceType":589,"tags":1777},"OpenClaw 安装与环境","按官方推荐方式安装 OpenClaw，并根据本地开发、WSL2 和生产部署场景选择合适的安装路径。","/docs/setup/installation",[666,1679,1778,1772],"install-script",{"title":1780,"description":1781,"path":1782,"category":1761,"updatedAt":681,"sourceType":589,"tags":1783},"安装器方式和升级路径怎么选","基于最新官方 Install 与 Updating 文档，整理 install.sh、install-cli.sh、PowerShell 安装器、全局包安装和 git 安装各自适合什么场景，以及后续升级时应该走哪条路径。","/docs/setup/installer-methods-and-upgrade-paths",[666,1784,1778,1785,1394],"updater","git",{"title":1787,"description":1788,"path":1789,"category":1761,"updatedAt":927,"sourceType":589,"tags":1790},"安装器、更新与卸载","基于官方安装器、更新和卸载文档，整理 OpenClaw 从首次安装到原地升级、服务移除和彻底卸载的完整维护路径。","/docs/setup/installer-update-and-uninstall",[666,1784,1791,1318,1394],"uninstall",{"title":1793,"description":1794,"path":1795,"category":1761,"updatedAt":927,"sourceType":589,"tags":1796},"Linux 安装指南","在 Linux 服务器和桌面上安装和配置 OpenClaw 的详细指南。","/docs/setup/linux-installation",[1091,666,676,1797],"server",{"title":1799,"description":1800,"path":1801,"category":1761,"updatedAt":927,"sourceType":589,"tags":1802},"macOS 安装指南","在 macOS 上安装和配置 OpenClaw 的详细指南。","/docs/setup/macos-installation",[816,666,676,1803],"apple",{"title":1805,"description":1806,"path":1807,"category":1808,"updatedAt":673,"sourceType":589,"tags":1809},"版本迁移与升级检查单","在 OpenClaw 版本升级前后，优先检查配置、CLI、认证和入口层变化，避免把升级直接变成线上事故。","/docs/setup/migration-guide","迁移",[1810,1811,1391,1812],"migration","upgrade","checklist",{"title":1814,"description":1815,"path":1816,"category":1761,"updatedAt":927,"sourceType":589,"tags":1817},"Windows 安装指南","在 Windows 上安装和配置 OpenClaw 的详细指南，推荐使用 WSL2。","/docs/setup/windows-installation",[1090,666,676,1772],{"count":1819,"latestDate":785,"items":1820},116,[1821,1829,1840,1847,1857,1865,1870,1879,1887,1893,1900,1907,1914,1922,1927,1937,1947,1954,1960,1970,1982,1990,1995,2001,2007,2015,2022,2028,2036,2042,2049,2055,2061,2067,2073,2079,2084,2090,2097,2103,2110,2116,2122,2127,2133,2139,2146,2152,2157,2168,2174,2180,2186,2193,2200,2206,2212,2218,2228,2234,2240,2245,2251,2256,2263,2269,2275,2280,2286,2292,2297,2303,2308,2314,2320,2326,2332,2338,2343,2348,2355,2361,2369,2374,2380,2388,2394,2400,2406,2413,2418,2423,2430,2435,2440,2446,2452,2459,2465,2470,2476,2481,2492,2500,2505,2513,2518,2525,2530,2536,2541,2547,2552,2560,2566,2572],{"title":1822,"description":1823,"path":1824,"category":1825,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1828},"OpenClaw 支持超过 50 个集成平台","OpenClaw 宣布已支持超过 50 个消息和生产力平台集成，成为最全面的 AI 助手解决方案。","/news/50-integrations","生态动态","2026-03-09","openclaw.ai",[1256,613,878],{"title":1830,"description":1831,"path":1832,"category":1833,"date":1834,"updatedAt":707,"sourceType":589,"source":1827,"tags":1835},"OpenClaw 与主流 AI 模型对比分析","深入对比 OpenClaw 支持的各类 AI 模型，帮助用户选择最适合自己需求的模型配置。","/news/ai-model-comparison","技术深度","2026-03-07",[732,1836,1837,1072,1838,1839],"comparison","gpt","llama","analysis",{"title":1841,"description":1842,"path":1843,"category":1844,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1845},"OpenClaw 支持多种 AI 模型选择","OpenClaw 支持 Anthropic Claude、OpenAI GPT 和本地模型，为用户提供灵活的 AI 选择。","/news/ai-model-flexibility","功能介绍",[1846,732,1072,1837,684],"ai",{"title":1848,"description":1849,"path":1850,"category":1851,"date":1852,"updatedAt":707,"sourceType":1527,"source":1853,"tags":1854},"OpenClaw API v2 正式发布","OpenClaw 发布全新 API v2 版本，带来更强大的功能、更好的性能和更完善的开发者体验。","/news/api-v2-release","产品更新","2026-03-10","github.com/openclaw/openclaw",[1241,1855,1856,1639],"v2","developer",{"title":1858,"description":1859,"path":1860,"category":1861,"date":1852,"updatedAt":1852,"sourceType":589,"source":1862,"tags":1863},"OpenClaw on AWS：云上一键部署指南发布","AWS 官方发布 OpenClaw on Lightsail 部署指南，用户可在 AWS 云平台快速部署自己的 AI 助手实例。","/news/aws-lightsail-deployment","云服务集成","AWS Blog",[797,1764,1765,1864],"lightsail",{"title":1866,"description":1867,"path":1868,"category":1851,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1869},"OpenClaw 浏览器自动化功能升级","OpenClaw 浏览器自动化功能迎来重大升级，支持更多操作和更好的稳定性。","/news/browser-automation-v2",[907,660,1391,1455],{"title":1871,"description":1872,"path":1873,"category":1844,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1874},"OpenClaw Canvas 实时可视化功能详解","深入了解 OpenClaw 的 Canvas 功能，如何使用 A2UI 语法创建交互式可视化界面。","/news/canvas-a2ui",[1875,1876,1877,1878],"canvas","a2ui","visualization","ui",{"title":1880,"description":1881,"path":1882,"category":1883,"date":927,"updatedAt":927,"sourceType":877,"source":1884,"tags":1885},"OpenClaw 中国社区热潮：本地化部署与中文教程需求激增","OpenClaw 在中国市场迎来爆发式增长，小红书、知乎等平台讨论热度持续攀升，中文教程和本地化部署成为用户最关注的话题。","/news/china-community-boom","社区动态","社区观察",[1763,877,642,1886],"localization",{"title":1888,"description":1889,"path":1890,"category":1825,"date":1826,"updatedAt":673,"sourceType":1527,"source":1891,"tags":1892},"ClawHub 技能市场突破 300 技能大关","OpenClaw 官方技能市场 ClawHub 已收录超过 300 个开源技能，为用户提供丰富的扩展选择。","/news/clawhub-300-skills","github.com/openclaw/clawhub",[626,860,878,716],{"title":1894,"description":1895,"path":1896,"category":1883,"date":1826,"updatedAt":673,"sourceType":877,"source":1897,"tags":1898},"OpenClaw 开发者社区突破 5 万人","OpenClaw 开发者社区持续增长，Discord 成员已超过 50,000 人。","/news/developer-community","discord.gg/openclaw",[877,854,622,1899],"growth",{"title":1901,"description":1902,"path":1903,"category":1904,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1905},"OpenClaw Discord 集成配置","了解如何将 Discord Bot 连接到 OpenClaw，实现服务器和频道管理。","/news/discord-integration","渠道指南",[854,1203,1906,642],"channel",{"title":1908,"description":1909,"path":1910,"category":1851,"date":1826,"updatedAt":673,"sourceType":1527,"source":1911,"tags":1912},"OpenClaw 企业部署最佳实践发布","OpenClaw 官方发布企业级部署指南，包含 Ansible 自动化、容器化部署和安全配置。","/news/enterprise-deployment","github.com/openclaw/openclaw-ansible",[632,1765,1913,1771],"ansible",{"title":1915,"description":1916,"path":1917,"category":1918,"date":1919,"updatedAt":707,"sourceType":589,"source":1827,"tags":1920},"OpenClaw 企业版功能详解","深入了解 OpenClaw 企业版的专属功能、部署方案和安全特性，助力企业数字化转型。","/news/enterprise-edition-guide","产品介绍","2026-03-06",[632,1765,594,1921],"features",{"title":1923,"description":1924,"path":1925,"category":1904,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1926},"OpenClaw 飞书集成配置","了解如何将 OpenClaw 集成到飞书，实现企业协作。","/news/feishu-integration",[943,944,1906,632,642],{"title":1928,"description":1929,"path":1930,"category":1931,"date":707,"updatedAt":707,"sourceType":877,"source":1932,"tags":1933},"OpenClaw 创始人 Peter Steinberger：从独立开发者到开源明星","OpenClaw 创始人 Peter Steinberger 的创业故事，从 Clawdbot/Moltbot 到爆火开源项目的历程。","/news/founder-story","人物故事","社区整理",[1934,1935,1936,877],"founder","story","opensource",{"title":1938,"description":1939,"path":1940,"category":1941,"date":1826,"updatedAt":673,"sourceType":1527,"source":1942,"tags":1943},"OpenClaw GitHub 星标突破 28.7 万","OpenClaw 开源项目在 GitHub 上的星标数突破 287,000，成为最受欢迎的开源 AI 助手项目之一。","/news/github-stars-milestone","项目动态","github.com/openclaw",[1527,1944,1945,1946],"stars","milestone","open-source",{"title":1948,"description":1949,"path":1950,"category":1851,"date":1951,"updatedAt":927,"sourceType":1527,"source":1853,"tags":1952},"OpenClaw 本地模型支持全面升级","OpenClaw 现已支持更多本地大语言模型，包括 Llama 3、Mistral、Qwen 等，让用户在保护隐私的同时享受 AI 能力。","/news/local-model-support","2026-03-05",[995,997,1838,1953,994],"mistral",{"title":1955,"description":1956,"path":1957,"category":1851,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1958},"OpenClaw macOS 伴侣应用 Beta 发布","OpenClaw 推出专为 macOS 15+ 设计的伴侣应用，提供更便捷的菜单栏访问体验。","/news/macos-companion-app",[816,1959,1457,1391],"app",{"title":1961,"description":1962,"path":1963,"category":1964,"date":1826,"updatedAt":673,"sourceType":1965,"source":1827,"tags":1966},"OpenClaw 获 MacStories 专题报道：个人 AI 助手的未来","知名科技媒体 MacStories 发表专题报道，高度评价 OpenClaw 为个人 AI 助手领域带来的创新。","/news/media-coverage","媒体报道","media",[1965,1967,1968,1969],"macstories","coverage","press",{"title":1971,"description":1972,"path":1973,"category":1974,"date":673,"updatedAt":673,"sourceType":770,"source":1975,"tags":1976},"外部报道：Meta 收购 Moltbook，OpenClaw 生态再次进入主流视野","根据 2026 年 3 月 11 日自动抓取的外部报道，Meta 已收购基于 OpenClaw 构建的 AI 代理社交网络 Moltbook。本文将事件背景、与 OpenClaw 的关联，以及对中文用户的参考价值整理为站点可读版本。","/news/meta-moltbook-openclaw-background","行业动态","自动抓取外部报道（2026-03-11）",[1977,1978,1979,1980,1981],"meta","moltbook","openclaw","ai-agent","industry",{"title":1983,"description":1984,"path":1985,"category":1851,"date":1986,"updatedAt":707,"sourceType":589,"source":1827,"tags":1987},"OpenClaw 移动端体验全面优化","OpenClaw 发布移动端重大更新，带来全新界面设计、性能优化和多项新功能。","/news/mobile-experience-update","2026-03-08",[841,1088,1089,1988,1989],"ux","performance",{"title":1991,"description":1992,"path":1993,"category":1851,"date":927,"updatedAt":707,"sourceType":1527,"source":1853,"tags":1994},"OpenClaw 多 Agent 协作功能正式发布","OpenClaw 发布多 Agent 协作功能，支持多个 AI 代理协同工作，实现复杂任务的自动化处理。","/news/multi-agent-collaboration",[717,947,659,660],{"title":1996,"description":1997,"path":1998,"category":1844,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":1999},"OpenClaw 多平台客户端详解","了解 OpenClaw 在 macOS、iOS、Android 等多平台上的客户端能力，以及如何实现跨设备无缝使用。","/news/multiplatform-clients",[2000,816,1088,1089,1087],"clients",{"title":2002,"description":2003,"path":2004,"category":1851,"date":1951,"updatedAt":673,"sourceType":1527,"source":1853,"tags":2005},"OpenClaw 2026.3.7 版本观察","结合最新 release 观察当前版本中最值得中文用户优先关注的变化方向。","/news/mvp-launch",[1391,2006,1392],"version",{"title":2008,"description":2009,"path":2010,"category":2011,"date":2012,"updatedAt":707,"sourceType":589,"source":1827,"tags":2013},"OpenClaw 开源一周年：回顾与展望","OpenClaw 开源项目迎来一周年里程碑，回顾这一年的成长历程和社区贡献。","/news/open-source-anniversary","官方公告","2026-03-01",[2014,1946,877,1945],"anniversary",{"title":2016,"description":2017,"path":2018,"category":1851,"date":2019,"updatedAt":681,"sourceType":1527,"source":2020,"tags":2021},"OpenClaw 2026.3.13 官方发布：Cron、插件碰撞、Docker 时区和网关稳定性继续修复","基于 2026 年 3 月 14 日发布的官方 GitHub Release，整理本轮最值得中文站读者关注的调度、插件、Docker、渠道和 UI 修复点。","/news/openclaw-2026-3-13-release","2026-03-14","https://github.com/openclaw/openclaw/releases",[1391,1392,788,716,1771,285],{"title":2023,"description":2024,"path":2025,"category":1851,"date":1717,"updatedAt":785,"sourceType":1527,"source":2026,"tags":2027},"OpenClaw 2026.4.1 发布：/tasks、SearXNG、Bedrock Guardrails 和 Feishu 评论流进入主线","2026 年 4 月 1 日的 OpenClaw 2026.4.1 版本，把后台任务板、SearXNG 搜索、Bedrock Guardrails 和 Feishu Drive 评论流一起推进到了更成熟的位置。","/news/openclaw-2026-4-1-release","https://github.com/openclaw/openclaw/releases/tag/v2026.4.1",[1391,787,1139,796,943,799],{"title":2029,"description":2030,"path":2031,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2033,"tags":2034},"OpenClaw 集成观察：HTTP API、Gateway WebSocket 与 SDK 的三层接口面正在被官方写清","基于 2026 年 3 月 25 日可见的官方 API、Web 与 Gateway 文档，最近开发者侧最值得关注的变化之一是不同接口面的分工正在被官方主动拆清。","/news/openclaw-api-surface-watch-2026-03-25","生态观察","https://docs.openclaw.ai/api/v2",[1241,1247,1639,285,2035],"integration",{"title":2037,"description":2038,"path":2039,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2040,"tags":2041},"OpenClaw 执行审批观察：CLI、per-agent allowlist 与聊天转发正在把宿主机执行面做成正式治理层","基于 2026 年 3 月 24 日可见的官方 approvals CLI 与 Exec Approvals 文档，最近最值得关注的信号不是“能不能审批”，而是宿主机执行边界已经开始形成一套完整治理面。","/news/openclaw-approvals-surface-watch-2026-03-24","https://docs.openclaw.ai/tools/exec-approvals",[931,929,1051,594,285,1482],{"title":2043,"description":2044,"path":2045,"category":2032,"date":1239,"updatedAt":1239,"sourceType":589,"source":2046,"tags":2047},"OpenClaw 开始把 AUTH_TOKEN_MISMATCH 写成可恢复的漂移场景","官方最新 Dashboard 文档把 AUTH_TOKEN_MISMATCH、trusted retry 和 token drift recovery 串成了一条更完整的恢复路径，让认证失败不再只是黑箱报错。","/news/openclaw-auth-mismatch-retry-watch-2026-03-26","https://docs.openclaw.ai/web/dashboard",[668,593,2048,1045,1306],"drift",{"title":2050,"description":2051,"path":2052,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2053,"tags":2054},"OpenClaw 的自动化运维面正在收成一条更清楚的排障梯子","官方最近围绕 Heartbeat、cron CLI 和 Automation Troubleshooting 的文档更新，正在把自动化问题从“感觉没触发”收敛成更可观测的几层：调度、入队、运行结果、可见性与时间窗口。","/news/openclaw-automation-ops-ladder-watch-2026-03-29","https://docs.openclaw.ai/automation/troubleshooting",[660,1292,788,1739,633],{"title":2056,"description":2057,"path":2058,"category":2032,"date":785,"updatedAt":785,"sourceType":589,"source":2059,"tags":2060},"OpenClaw 正在把 /tasks 做成后台工作总账本，而不是聊天里的附属提示","官方近期补全的 Background Tasks 与 tasks CLI 文档，说明 OpenClaw 的后台任务体系已经从隐式执行，转向更正式的 ledger、审计和清理模型。","/news/openclaw-background-tasks-watch-2026-04-30","https://docs.openclaw.ai/automation/tasks",[787,660,788,789,1413,633],{"title":2062,"description":2063,"path":2064,"category":2032,"date":785,"updatedAt":785,"sourceType":589,"source":2065,"tags":2066},"OpenClaw 的 Amazon Bedrock 接入开始把 Guardrails 正式推到 provider 层","官方近期完善的 Amazon Bedrock 文档，把 AWS credential chain、自动发现和 Guardrails 全部写到了同一页里，说明 Bedrock 正在从能接入走向能治理。","/news/openclaw-bedrock-guardrails-watch-2026-04-30","https://docs.openclaw.ai/providers/bedrock",[796,797,799,798,1098],{"title":2068,"description":2069,"path":2070,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2071,"tags":2072},"OpenClaw 开始把 Broadcast Groups 从路由技巧推进成多代理协作入口","官方最新 Broadcast Groups 文档把多 agent 同群运行的触发条件、session 隔离和处理策略写得更完整了，也让它和普通 bindings 的分工更清楚。","/news/openclaw-broadcast-groups-watch-2026-03-25","https://docs.openclaw.ai/channels/broadcast-groups",[824,808,825,807,853],{"title":2074,"description":2075,"path":2076,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2077,"tags":2078},"OpenClaw 的浏览器管理员面正在收成一条完整信任链","官方最近围绕 Pairing、Remote Access、Trusted Proxy Auth 和 Dashboard 的文档更新，正在把浏览器入口从“页面能打开”收敛成“地址、认证、设备与 operator 权限”四层联动的信任链。","/news/openclaw-browser-trust-chain-watch-2026-03-29","https://docs.openclaw.ai/gateway/trusted-proxy-auth",[668,20,965,683,594],{"title":2080,"description":2081,"path":2082,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2040,"tags":2083},"OpenClaw 渠道观察：Telegram 和 Discord 正在从聊天入口扩展成正式审批面","基于 2026 年 3 月 24 日可见的官方 Exec Approvals 文档，Telegram 与 Discord 最近最值得关注的变化不是又多了一个命令，而是它们已经开始承担受控审批入口。","/news/openclaw-channel-approval-clients-watch-2026-03-24",[852,854,931,613,1404],{"title":2085,"description":2086,"path":2087,"category":1883,"date":608,"updatedAt":608,"sourceType":877,"source":2088,"tags":2089},"OpenClaw 在中国 AI 生态中的位置：从中文教程热到本地化能力竞赛","基于 2026 年 3 月 16 日整理素材，梳理 OpenClaw 在中国 AI 生态里的关注点：本地部署、中文模型接入、数据安全与本土服务集成。","/news/openclaw-china-ecosystem-watch-2026-03-16","content/tmp/2026-03-16/openclaw-china-ai-ecosystem-analysis.md",[1763,878,1886,1839],{"title":2091,"description":2092,"path":2093,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2094,"tags":2095},"OpenClaw ClawHub 观察：sync、lockfile 与最小 telemetry 让技能注册表更像正式分发生态","基于 2026 年 3 月 24 日可见的官方 ClawHub 文档，最近最值得关注的变化不是“技能数量”，而是技能分发、版本记录和同步行为正在更像一套正式 registry。","/news/openclaw-clawhub-sync-watch-2026-03-24","https://docs.openclaw.ai/tools/clawhub",[860,626,869,870,2096,861],"telemetry",{"title":2098,"description":2099,"path":2100,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2101,"tags":2102},"OpenClaw CLI 观察：命令行已经不只是辅助工具，而是在慢慢收敛成正式控制面","基于 2026 年 3 月 21 日可见的官方 CLI Reference、Gateway protocol 与 Dashboard 文档，整理最近最值得中文站关注的 CLI 变化：status/health/logs 分层、gateway RPC 边界，以及 Dashboard 和 CLI 之间更清晰的协作关系。","/news/openclaw-cli-control-plane-watch-2026-03-21","https://docs.openclaw.ai/cli",[790,285,1602,780,633],{"title":2104,"description":2105,"path":2106,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2107,"tags":2108},"OpenClaw 的配置分层边界越来越清楚","官方最近围绕 Environment Variables、Configuration、Logging 和 Debugging 的文档更新，正在把正式配置、env 注入和一次性 override 拆成更清楚的层。","/news/openclaw-configuration-layering-watch-2026-03-22","https://docs.openclaw.ai/help/environment",[625,1173,806,2109,633],"overrides",{"title":2111,"description":2112,"path":2113,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2020,"tags":2114},"OpenClaw 上下文观察：Compaction、Session 连续性与 persona 保真正在成为官方显式关注点","基于 2026 年 3 月 21 日可见的官方 Context 文档与 GitHub Releases 页面，整理最近最值得中文站关注的上下文变化：compaction 后 token 检查、session continuity、persona/language 保真，以及它们对长期使用的意义。","/news/openclaw-context-compaction-watch-2026-03-21",[1195,1196,764,615,2115],"continuity",{"title":2117,"description":2118,"path":2119,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2120,"tags":2121},"OpenClaw 控制面观察：Control UI、设备配对与 Tailscale Serve 正在把浏览器管理做成正式能力","基于 2026 年 3 月 21 日可见的官方 Control UI、Dashboard、Pairing 与 Tailscale 文档，整理最近最值得关注的控制面变化：浏览器设备配对、语言支持、远程 Serve 与更明确的管理面边界。","/news/openclaw-control-surface-watch-2026-03-21","https://docs.openclaw.ai/web/control-ui",[886,668,1278,965,683],{"title":2123,"description":2124,"path":2125,"category":2032,"date":1239,"updatedAt":1239,"sourceType":589,"source":2046,"tags":2126},"OpenClaw 正在把 Dashboard bootstrap 写成更安全的默认路径","官方最新 Dashboard 文档更明确地说明了 openclaw dashboard 在 localhost、SecretRef token 和 headless 环境里的引导行为，也让它更像正式控制面入口。","/news/openclaw-dashboard-bootstrap-watch-2026-03-26",[668,763,1553,593,886],{"title":2128,"description":2129,"path":2130,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2046,"tags":2131},"OpenClaw Web 控制面观察：Dashboard 与 WebChat 的认证引导和回流边界正在变清楚","基于 2026 年 3 月 24 日可见的官方 dashboard CLI、Web Dashboard 与 WebChat 文档，最近 Web 控制面最值得关注的变化是认证引导、SecretRef token 处理和 WebChat 回流边界正在被主动写清。","/news/openclaw-dashboard-webchat-auth-watch-2026-03-24",[668,739,906,1553,807,2132],"web",{"title":2134,"description":2135,"path":2136,"category":1825,"date":608,"updatedAt":608,"sourceType":877,"source":2137,"tags":2138},"OpenClaw 开发者生态扩张观察：中文技能与本地工作流成为新增长点","基于 2026 年 3 月 16 日临时素材，整理 OpenClaw 开发者生态在中文社区中的扩展方向，重点关注中文技能、本地平台集成与企业工作流落地。","/news/openclaw-developer-ecosystem-watch-2026-03-16","content/tmp/2026-03-16/openclaw-developer-ecosystem-expansion.md",[622,626,878,1763],{"title":2140,"description":2141,"path":2142,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2143,"tags":2144},"OpenClaw 的 devices CLI 正在把设备授权写成一条完整生命周期","官方最近围绕 devices CLI 的补强，让 approve、revoke、rotate 和 fresh token 不再像零散命令，而更像完整的设备授权生命周期。","/news/openclaw-device-token-lifecycle-watch-2026-03-25","https://docs.openclaw.ai/channels/pairing",[966,965,906,1312,2145],"rotate",{"title":2147,"description":2148,"path":2149,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2150,"tags":2151},"OpenClaw 的诊断与修复工作流正在成型","官方最近围绕 Doctor、Diagnostics Flags、Debugging 和 sessions cleanup 的文档更新，正在把 OpenClaw 的排障方式从“看日志猜”推进到更清楚的 repair ladder。","/news/openclaw-diagnostics-repair-watch-2026-03-22","https://docs.openclaw.ai/doctor",[1318,1476,1319,1561,633],{"title":2153,"description":2154,"path":2155,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2150,"tags":2156},"OpenClaw 排障观察：doctor 正在从“检查器”继续长成带备份心智的修复入口","基于 2026 年 3 月 25 日可见的官方 Doctor 文档，最近排障层最值得关注的变化之一是 doctor 对 stale config、unknown keys 和 legacy 状态的处理边界越来越清楚。","/news/openclaw-doctor-repair-boundary-watch-2026-03-25",[1318,1319,1170,1394,1476],{"title":2158,"description":2159,"path":2160,"category":2161,"date":608,"updatedAt":608,"sourceType":877,"source":2162,"tags":2163},"OpenClaw 教育场景观察：AI 助教、个性化学习与高校试点想象空间","基于 2026 年 3 月 16 日教育领域临时稿，梳理 OpenClaw 在高校与教学场景中的潜在落地方向，包括答疑、学习路径推荐和教师工作流辅助。","/news/openclaw-education-adoption-watch-2026-03-16","行业观察","content/tmp/2026-03-16/openclaw-education-sector-adoption.md",[2164,2165,2166,2167],"education","adoption","ai-tutor","higher-education",{"title":2169,"description":2170,"path":2171,"category":2161,"date":608,"updatedAt":608,"sourceType":877,"source":2172,"tags":2173},"OpenClaw 企业应用热度上升：中文团队更关注私有化部署与流程接入","基于 2026 年 3 月 16 日企业方向临时稿，整理 OpenClaw 在中文企业场景中的关注重点，包括私有化部署、安全边界、行业接入与内部工作流自动化。","/news/openclaw-enterprise-adoption-watch-2026-03-16","content/tmp/2026-03-16/openclaw-enterprise-adoption-boom.md",[632,1765,659,1763],{"title":2175,"description":2176,"path":2177,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2178,"tags":2179},"OpenClaw 扩展层观察：ClawHub、插件托管 hooks 与 onboarding 勾选正在把扩展能力收拢成一条更完整链路","基于 2026 年 3 月 21 日可见的官方 Skills、ClawHub、Plugins 与 Hooks 文档，整理最近最值得中文站关注的扩展层变化：技能 registry、插件托管 hooks，以及 onboarding 阶段对推荐 hooks 的直接引导。","/news/openclaw-extension-stack-watch-2026-03-21","https://docs.openclaw.ai/automation/hooks",[626,860,716,718,879],{"title":2181,"description":2182,"path":2183,"category":2032,"date":785,"updatedAt":785,"sourceType":589,"source":2184,"tags":2185},"OpenClaw 的 Feishu 入口正在从聊天机器人走向文档协作流","官方近期更新的 Feishu 文档，把扫码接入、群控边界和 Drive 评论线程动作都写进了主线，说明 Feishu 已经不只是简单聊天入口。","/news/openclaw-feishu-drive-comments-watch-2026-04-30","https://docs.openclaw.ai/channels/feishu",[943,944,945,946,613,947],{"title":2187,"description":2188,"path":2189,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2190,"tags":2191},"OpenClaw 正在把 gateway-owned pairing 的过期与轮换边界说清楚","官方最新 Gateway-owned pairing 文档把 pending request 的 5 分钟过期、fresh token 生成和 UI 只是审批前端这几层边界写得更清楚了。","/news/openclaw-gateway-pairing-expiry-watch-2026-03-25","https://docs.openclaw.ai/gateway/pairing",[285,965,2192,906,779],"pending",{"title":2194,"description":2195,"path":2196,"category":2032,"date":1239,"updatedAt":1239,"sourceType":589,"source":2197,"tags":2198},"OpenClaw 正在把 Gateway 的 session source-of-truth 地位写得更明确","官方最新 Session 文档更明确地说明 session store、JSONL transcript 和 token 计数都应围绕 Gateway 理解，这会直接影响 WebChat、Dashboard 和远程 operator 的排障方式。","/news/openclaw-gateway-source-of-truth-watch-2026-03-26","https://docs.openclaw.ai/session",[285,826,739,668,2199],"state",{"title":2201,"description":2202,"path":2203,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2204,"tags":2205},"OpenClaw 开始把群聊入口判断顺序写成可复述规则","官方最近在 Groups、Group Messages 和 Messages 文档里，把群入口的 groupPolicy、allowlist 和 mention gating 顺序写得更完整了，也让“没回”和“没进系统”首次更容易区分。","/news/openclaw-group-policy-watch-2026-03-25","https://docs.openclaw.ai/channels/groups",[825,1625,1051,984,807],{"title":2207,"description":2208,"path":2209,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2204,"tags":2210},"OpenClaw 正在把群触发从“@一下就行”写成更完整的治理链","官方最近围绕 Groups、Group Messages 和 Broadcast Groups 的文档更新，正在把 reply-to implicit mention、pending history、forum topic session key 和 shared-group rollout 写成更完整的群入口治理链。","/news/openclaw-group-trigger-governance-watch-2026-03-29",[825,1698,2211,824,1098],"activation",{"title":2213,"description":2214,"path":2215,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2216,"tags":2217},"OpenClaw 配置观察：include 合并边界正在从“能拆文件”继续走向“能预测最终结果”","基于 2026 年 3 月 25 日可见的官方 Configuration 文档，最近配置层最值得关注的变化之一是 include、数组处理和 sibling override 的顺序正在被官方主动写清。","/news/openclaw-include-merge-boundary-watch-2026-03-25","https://docs.openclaw.ai/gateway/configuration",[625,1645,1270,1646,633],{"title":2219,"description":2220,"path":2221,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2222,"tags":2223},"OpenClaw 官方 Showcase 基础设施观察：Home Assistant、Nix 与远程文件流转正在成为高频落地方向","基于 2026 年 3 月 21 日可见的官方 Showcase 页面，整理最近最值得关注的基础设施与部署类案例，观察 OpenClaw 在家庭服务器、可复现部署和远程实例运维上的真实应用。","/news/openclaw-infra-showcase-watch-2026-03-21","https://docs.openclaw.ai/start/showcase",[2224,1765,2225,2226,2227],"showcase","home-assistant","nix","infrastructure",{"title":2229,"description":2230,"path":2231,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2232,"tags":2233},"OpenClaw 的长期会话治理能力正在变完整","官方最近围绕 session、memory、compaction 和 secure DM mode 的文档更新，正在把长期连续性、上下文边界和重置策略拼成一条更完整的治理链。","/news/openclaw-long-session-governance-watch-2026-03-22","https://docs.openclaw.ai/concepts/session",[764,615,1196,2115,1098],{"title":2235,"description":2236,"path":2237,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2238,"tags":2239},"OpenClaw 的后台维护生命周期正在变清楚","官方最近围绕 cron、sessions cleanup、doctor 和 retention 的文档更新，正在把长期运行时的会话、日志和作业痕迹分成更清楚的维护层次。","/news/openclaw-maintenance-lifecycle-watch-2026-03-22","https://docs.openclaw.ai/cron",[1394,788,764,1285,633],{"title":2241,"description":2242,"path":2243,"category":1851,"date":1826,"updatedAt":673,"sourceType":1527,"source":1853,"tags":2244},"OpenClaw 2026年3月版本更新：技能系统与安全性全面升级","OpenClaw 发布重要更新，带来性能优化、全新技能系统和安全性改进。","/news/openclaw-march-2026-update",[1391,1455,1392,626,594],{"title":2246,"description":2247,"path":2248,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2249,"tags":2250},"OpenClaw 记忆观察：Markdown 仍然是 source of truth，memory plugin slot 正在把索引层做成可切换能力","基于 2026 年 3 月 24 日可见的官方 Memory、CLI memory 与 Plugins 文档，最近最值得关注的变化之一是记忆体系的文件事实层和插件增强层正在被官方主动拆清。","/news/openclaw-memory-plugin-slot-watch-2026-03-24","https://docs.openclaw.ai/concepts/memory",[615,716,1019,1011,1026],{"title":2252,"description":2253,"path":2254,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2249,"tags":2255},"OpenClaw 正在把记忆检索从“向量搜索”写成一条完整流水线","官方最近围绕 Memory 和 memory CLI 的文档更新，正在把 hybrid search、重排、temporal decay、session indexing 和 embedding cache 逐步写成一条更完整的检索链。","/news/openclaw-memory-retrieval-pipeline-watch-2026-03-29",[615,1661,1658,1027,1151],{"title":2257,"description":2258,"path":2259,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2222,"tags":2260},"OpenClaw 官方 Showcase 记忆观察：WhatsApp Memory Vault、Karakeep 与中文学习 Skill 正在把语音和知识流转成长期资产","基于 2026 年 3 月 21 日可见的官方 Showcase 页面，整理最近最值得中文站关注的记忆与知识类案例，观察 OpenClaw 如何把转录、向量检索和学习流程接成长链路。","/news/openclaw-memory-showcase-watch-2026-03-21",[2224,615,914,2261,2262],"vector-search","knowledge",{"title":2264,"description":2265,"path":2266,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2267,"tags":2268},"OpenClaw 的 mention gating 正在从单一 @ 规则变成跨渠道触发层","官方最新 Groups 和 Group Messages 文档显示，mention gating 已经不再只服务 WhatsApp 群，而是在 Telegram、Slack、Discord、iMessage 等入口上逐步形成统一触发层。","/news/openclaw-mention-gating-watch-2026-03-25","https://docs.openclaw.ai/channels/group-messages",[1625,825,852,854,921],{"title":2270,"description":2271,"path":2272,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2273,"tags":2274},"OpenClaw 的消息入口语义正在变清楚","官方最近围绕 Messages、WebChat 和 Channel Routing 的文档更新，正在把消息入口、上下文桶、历史展示和投递节奏拆成更明确的几层。","/news/openclaw-message-surface-watch-2026-03-22","https://docs.openclaw.ai/messages",[984,739,807,988,613],{"title":2276,"description":2277,"path":2278,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2101,"tags":2279},"OpenClaw 模型观察：models status 正在从状态展示继续长成探活入口","基于 2026 年 3 月 24 日可见的官方 CLI 文档，最近模型层最值得关注的变化之一是 models status 已经不只负责展示主模型和 fallback，而是开始承担 auth profile 探测。","/news/openclaw-model-probe-watch-2026-03-24",[732,1667,798,593,1355],{"title":2281,"description":2282,"path":2283,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2284,"tags":2285},"OpenClaw 节点观察：headless node、普通设备节点与 Gateway 的宿主边界正在被官方写清","基于 2026 年 3 月 25 日可见的官方 Nodes、Architecture 与 Pairing 文档，最近节点层最值得关注的变化之一是能力宿主边界正在被主动拆清。","/news/openclaw-node-host-boundary-watch-2026-03-25","https://docs.openclaw.ai/nodes",[779,964,285,965,966],{"title":2287,"description":2288,"path":2289,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2290,"tags":2291},"OpenClaw 接入观察：从 2026.1.29 的迁移信号到现在的 Onboarding Wizard，官方已经把“第一次跑通”做成更完整链路","基于 2026 年 3 月 21 日可见的官方 Onboarding、Install 与 Releases 页面，整理 OpenClaw 从命名迁移、路径自动迁移到本地/远程 wizard 分流这条接入链路最近最值得注意的变化。","/news/openclaw-onboarding-migration-watch-2026-03-21","https://docs.openclaw.ai/start/wizard",[667,1810,1092,1811,1394],{"title":2293,"description":2294,"path":2295,"category":2032,"date":1239,"updatedAt":1239,"sourceType":589,"source":2120,"tags":2296},"OpenClaw 的远程 operator 正在从“谁都能开网页”转向浏览器级交接管理","随着 Dashboard、Control UI 和 device pairing 文档持续补强，官方越来越清楚地把浏览器 profile、设备 pairing 和控制面交接写成同一条管理面问题。","/news/openclaw-operator-browser-watch-2026-03-26",[1404,907,886,965,683],{"title":2298,"description":2299,"path":2300,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2301,"tags":2302},"OpenClaw 正在把 Dashboard、WebChat 和 WebSocket 收成一套 operator surface","官方最近围绕 Dashboard、WebChat 和 Gateway Protocol 的文档更新，越来越清楚地把这些入口解释成同一套 operator surface 的不同层，而不是彼此割裂的功能页。","/news/openclaw-operator-surface-convergence-watch-2026-03-29","https://docs.openclaw.ai/gateway/protocol",[668,739,1247,1404,780],{"title":2304,"description":2305,"path":2306,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2143,"tags":2307},"OpenClaw 的 pairing CLI 正在从单条 approve 命令长成正式入口治理面","官方最近把 pairing CLI 的 list、clear、--account 和 --notify 等行为写得更完整了，也让聊天入口审批越来越像一套正式的运营控制面。","/news/openclaw-pairing-cli-scope-watch-2026-03-25",[965,1505,613,1506,633],{"title":2309,"description":2310,"path":2311,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2312,"tags":2313},"OpenClaw 官方插件生态观察：社区插件、内置 Provider 插件与 Hook Pack 正在形成更完整扩展层","基于 2026 年 3 月 21 日可见的官方插件与 hooks 文档，整理 OpenClaw 插件生态最近最值得关注的三个变化：社区插件目录、package pack、多层 hooks 组织方式。","/news/openclaw-plugin-ecosystem-watch-2026-03-21","https://docs.openclaw.ai/plugins",[716,878,718,877,879],{"title":2315,"description":2316,"path":2317,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2318,"tags":2319},"OpenClaw 插件观察：安装 spec 和 update tracking 正在决定插件后续会沿哪条轨道走","基于 2026 年 3 月 24 日可见的官方 plugins CLI 文档，最近插件层最值得关注的变化之一是 install spec、--pin 与 plugins.installs 正在被官方主动连成一条生命周期链。","/news/openclaw-plugin-install-tracking-watch-2026-03-24","https://docs.openclaw.ai/cli/plugins",[716,860,1679,1680,1393],{"title":2321,"description":2322,"path":2323,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2324,"tags":2325},"OpenClaw 工作流观察：OpenProse 与 Lobster 的上下层分工正在变清楚","基于 2026 年 3 月 24 日可见的官方 Lobster 文档，最近最值得关注的信号是 OpenProse 与 Lobster 的边界正在被官方主动写清，多智能体准备和确定性执行不再混成一层。","/news/openclaw-prose-lobster-watch-2026-03-24","https://docs.openclaw.ai/tools/lobster",[1079,1080,659,931,717],{"title":2327,"description":2328,"path":2329,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2330,"tags":2331},"OpenClaw 正在把 provider、模型和远程执行分成不同治理层","官方最近围绕 Models、Model Failover 和 node 的文档更新，正在把 provider auth、模型 allowlist、多模态能力和远程 node 执行拆成更清楚的治理层。","/news/openclaw-provider-capability-governance-watch-2026-03-29","https://docs.openclaw.ai/concepts/models",[798,732,779,593,1098],{"title":2333,"description":2334,"path":2335,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2336,"tags":2337},"OpenClaw 的 provider 故障恢复正在变成一条更清楚的梯子","官方最近围绕 Model Failover、Gateway Troubleshooting、LiteLLM 和 Cloudflare AI Gateway 的文档更新，正在把模型故障从“直接换模型”收敛成更清楚的几层：能力条件、profile 轮转、统一网关和跨模型 fallback。","/news/openclaw-provider-recovery-ladder-watch-2026-03-29","https://docs.openclaw.ai/concepts/model-failover",[798,1469,732,285,633],{"title":2339,"description":2340,"path":2341,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2020,"tags":2342},"OpenClaw 发布观察：2026.3.13 恢复型 Release 暴露出版本跟踪里最容易忽略的三层差异","基于 2026 年 3 月 21 日可见的 GitHub Releases 页面，整理 OpenClaw 2026.3.13 恢复型 Release 的关键信号，以及中文站在跟踪版本时最该注意的 npm 版本、Git tag 和 GitHub Release 名称差异。","/news/openclaw-release-watch-2026-03-21",[1391,1392,1394,1393],{"title":2344,"description":2345,"path":2346,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2046,"tags":2347},"OpenClaw 的远程管理员面边界越来越清楚","官方最近围绕 Dashboard、Pairing、Gateway-owned pairing 与 nodes 的文档更新，正在把远程协作、浏览器入口和设备接入的边界拆得更清楚。","/news/openclaw-remote-admin-watch-2026-03-22",[668,965,779,683,1299],{"title":2349,"description":2350,"path":2351,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2352,"tags":2353},"OpenClaw 的 routing precedence 正在成为更明确的排障坐标系","官方最近围绕 Channel Routing 的写法，正在把 peer、thread inheritance、guild、team、account 和 channel 等命中层级固定下来，让路由排障越来越像查规则，而不是猜模型。","/news/openclaw-routing-precedence-watch-2026-03-25","https://docs.openclaw.ai/channels/channel-routing",[807,806,2354,613,808],"threads",{"title":2356,"description":2357,"path":2358,"category":2032,"date":785,"updatedAt":785,"sourceType":589,"source":2359,"tags":2360},"OpenClaw 把 SearXNG 推进 bundled web_search provider，搜索层开始更适合自托管","官方近期上线的 SearXNG Search 文档，说明 OpenClaw 的 web_search 已经不只适合外部 API，也开始正式支持自托管聚合搜索。","/news/openclaw-searxng-search-watch-2026-04-30","https://docs.openclaw.ai/tools/searxng-search",[1139,1026,1140,709,614],{"title":2362,"description":2363,"path":2364,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2365,"tags":2366},"OpenClaw Secret 观察：active snapshot 正在把密钥轮换从“即时取值”收成“原子切换”","基于 2026 年 3 月 25 日可见的官方 Secrets Management 文档，最近 secrets 层最值得关注的变化之一是 active snapshot 与 last-known-good 的边界越来越清楚。","/news/openclaw-secret-snapshot-watch-2026-03-25","https://docs.openclaw.ai/gateway/secrets",[1707,2367,2368,1706,633],"snapshot","rotation",{"title":2370,"description":2371,"path":2372,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2232,"tags":2373},"OpenClaw 正在把 secure DM mode 写成共享入口的默认安全心智","官方最近围绕 Session、Security 和 CLI Security 的更新，正在把 secure DM mode 从一个可选技巧，推成多人 DM 入口的基础隔离建议。","/news/openclaw-secure-dm-mode-watch-2026-03-25",[826,594,1576,965,1428],{"title":2375,"description":2376,"path":2377,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2378,"tags":2379},"OpenClaw 安全观察：security audit 已经从提醒工具继续长成加固入口","基于 2026 年 3 月 24 日可见的官方安全文档，最近最值得关注的信号是 openclaw security audit 不再只是列问题，而是在形成 audit、deep、fix 三段式加固路径。","/news/openclaw-security-audit-fix-watch-2026-03-24","https://docs.openclaw.ai/gateway/security",[594,1413,1415,1414,633],{"title":2381,"description":2382,"path":2383,"category":2384,"date":608,"updatedAt":608,"sourceType":877,"source":2385,"tags":2386},"OpenClaw 安全与合规话题升温：中文团队更在意可审计与本地数据边界","基于 2026 年 3 月 16 日安全方向临时稿，整理 OpenClaw 在中文环境下最受关注的安全议题，包括本地运行、合规要求、可审计性与金融等高敏行业采用。","/news/openclaw-security-compliance-watch-2026-03-16","安全观察","content/tmp/2026-03-16/openclaw-security-audit-milestone.md",[594,2387,997,632],"compliance",{"title":2389,"description":2390,"path":2391,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2365,"tags":2392},"OpenClaw 的安全运维边界继续细化","官方最近围绕 Secrets、approvals forwarding、trusted proxy 和 Control UI 降级开关的文档，正在把安全问题从抽象原则推向更可执行的运维边界。","/news/openclaw-security-ops-watch-2026-03-22",[594,1706,931,2393,633],"proxy",{"title":2395,"description":2396,"path":2397,"category":2032,"date":1717,"updatedAt":1717,"sourceType":589,"source":2398,"tags":2399},"OpenClaw 正在把 session transcript 从 JSONL 文件写成结构化会话事实层","官方最近新增的 Session Management Deep Dive 文档，把 session header、message tree、compaction entry 和 branch summary 这几层边界写得更清楚了。","/news/openclaw-session-jsonl-deep-dive-watch-2026-04-01","https://docs.openclaw.ai/reference/session-management-compaction",[826,1720,1196,1719,285],{"title":2401,"description":2402,"path":2403,"category":2032,"date":1717,"updatedAt":1717,"sourceType":589,"source":2404,"tags":2405},"OpenClaw 的 sessions CLI 正在从会话列表命令长成 store 巡检入口","官方最近把 sessions CLI 的 scope、all-agents、active 和显式 store 路径写得更完整了，也让它更适合作为长期运维里的 session store 巡检面。","/news/openclaw-sessions-cli-watch-2026-04-01","https://docs.openclaw.ai/cli/sessions",[764,790,1726,1413,633],{"title":2407,"description":2408,"path":2409,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2410,"tags":2411},"OpenClaw 正在把 shared inbox 明确限定为协作硬化，而不是多租户承诺","官方最新 security audit 文档正在更明确地区分协作型 shared inbox 与互不信任多租户环境，并把 secure DM、sandbox 和 workspace-scoped access 组合成更完整的加固建议。","/news/openclaw-shared-inbox-trust-model-watch-2026-03-25","https://docs.openclaw.ai/cli/security",[594,1428,1429,2412,285],"sandbox",{"title":2414,"description":2415,"path":2416,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2222,"tags":2417},"OpenClaw 官方 Showcase 更新：Telegram PR 反馈、酒窖 Skill 与 Tesco 自动购物成为新样板","基于 2026 年 3 月 21 日可见的官方 Showcase 页面，整理最近最值得中文站关注的三个社区案例，观察 OpenClaw 在评审、个人数据库和购物自动化上的真实落地方式。","/news/openclaw-showcase-watch-2026-03-21",[2224,877,852,626,660],{"title":2419,"description":2420,"path":2421,"category":2032,"date":832,"updatedAt":832,"sourceType":589,"source":2410,"tags":2422},"OpenClaw 正在把团队入口治理拆成更细的几层","官方最近围绕 security audit、session、broadcast groups 和 channel routing 的文档更新，正在把 shared-user ingress、identityLinks、broadcast precedence 和 shared inbox 硬化拆成更清楚的治理面。","/news/openclaw-team-ingress-governance-watch-2026-03-29",[1428,1577,824,807,594],{"title":2424,"description":2425,"path":2426,"category":2032,"date":1717,"updatedAt":1717,"sourceType":589,"source":2427,"tags":2428},"OpenClaw 正在把 transcript hygiene 从隐藏兼容层写成正式参考边界","官方最近单独写出 Transcript Hygiene 文档后，tool call 修补、图片清理和 provider fixups 不再只是内部细节，而成了更清楚的运行前兼容层。","/news/openclaw-transcript-hygiene-watch-2026-04-01","https://docs.openclaw.ai/zh-CN/reference/transcript-hygiene",[1719,798,1745,1746,2429],"compatibility",{"title":2431,"description":2432,"path":2433,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2077,"tags":2434},"OpenClaw 远程入口观察：trusted-proxy 正在被官方明确定义为高收益但高责任模式","基于 2026 年 3 月 24 日可见的官方 trusted-proxy auth 文档，最近最值得关注的不是怎么把页面转发出来，而是 OpenClaw 正在主动强调 trusted-proxy 的安全责任转移。","/news/openclaw-trusted-proxy-risk-watch-2026-03-24",[20,594,683,285,593],{"title":2436,"description":2437,"path":2438,"category":2032,"date":1239,"updatedAt":1239,"sourceType":589,"source":2197,"tags":2439},"OpenClaw 的 UI 和 API 排障正在越来越像按层定位，而不是猜谁错了","官方最新 Session、WebChat 和 API 文档共同强化了一条思路：状态冲突时先回到 Gateway 事实层，再区分 UI 投影视图和 API 结构化返回。","/news/openclaw-ui-api-debug-watch-2026-03-26",[285,739,1241,1561,826],{"title":2441,"description":2442,"path":2443,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2444,"tags":2445},"OpenClaw 维护观察：卸载边界正在从“删包”变成“服务、状态、profile 与远程主机”的完整收口","基于 2026 年 3 月 24 日可见的官方 Updating 与 uninstall 文档，最近最值得关注的变化之一是 OpenClaw 的卸载和移除边界正在被官方主动写清，不再只是删除 CLI。","/news/openclaw-uninstall-boundaries-watch-2026-03-24","https://docs.openclaw.ai/cli/uninstall",[1791,1394,1073,285,2199],{"title":2447,"description":2448,"path":2449,"category":2032,"date":724,"updatedAt":724,"sourceType":589,"source":2450,"tags":2451},"OpenClaw 更新观察：stable、beta、dev 正在从版本标签变成正式 rollout 体系","基于 2026 年 3 月 24 日可见的官方 update CLI 与 Updating 文档，最近最值得关注的变化之一是更新通道和 auto-updater 行为已经被官方写成一套明确的 rollout 逻辑。","/news/openclaw-update-channels-watch-2026-03-24","https://docs.openclaw.ai/cli/update",[1455,1456,1457,1458,1459],{"title":2453,"description":2454,"path":2455,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2222,"tags":2456},"OpenClaw 官方 Showcase 语音观察：Phone Bridge、Telegram Voice Notes 与多语言转录正在把语音入口做实","基于 2026 年 3 月 21 日可见的官方 Showcase 页面，整理最近最值得中文站关注的语音与电话类案例，观察 OpenClaw 在电话桥接、TTS 回传和多语言转录上的真实方向。","/news/openclaw-voice-phone-showcase-watch-2026-03-21",[2224,900,2457,2458,914],"phone","tts",{"title":2460,"description":2461,"path":2462,"category":2032,"date":822,"updatedAt":822,"sourceType":589,"source":2463,"tags":2464},"OpenClaw 语音观察：全局 wake words 与设备本地 toggle 的分层正在变清楚","基于 2026 年 3 月 25 日可见的官方 Voice Wake 文档，最近语音层最值得关注的变化之一是 Gateway 级词表与设备本地开关的边界正在被官方主动强调。","/news/openclaw-voice-wake-boundary-watch-2026-03-25","https://docs.openclaw.ai/nodes/voice-wake",[900,1227,1228,779,966],{"title":2466,"description":2467,"path":2468,"category":1825,"date":681,"updatedAt":681,"sourceType":589,"source":2046,"tags":2469},"OpenClaw Web 入口观察：Dashboard、WebChat 与 Gateway WebSocket 正在收敛成一套更清晰的使用分工","基于 2026 年 3 月 21 日可见的官方 Dashboard、WebChat 与架构文档，整理最近最值得中文站关注的 Web 入口变化：Dashboard 的快速打开、WebChat 的 Gateway 直连，以及控制面和聊天面的职责分离。","/news/openclaw-web-surfaces-watch-2026-03-21",[668,739,1247,886,2132],{"title":2471,"description":2472,"path":2473,"category":2032,"date":1239,"updatedAt":1239,"sourceType":589,"source":2474,"tags":2475},"OpenClaw 正在把 WebChat、Dashboard 和 API 的入口职责写得更清楚","官方最近围绕 WebChat、Session 和 API 的写法，让 Dashboard 更像控制面、WebChat 更像会话 UI、API 更像结构化集成面，入口分工正在变得更稳定。","/news/openclaw-webchat-control-surface-watch-2026-03-26","https://docs.openclaw.ai/web/webchat",[739,668,1241,285,937],{"title":2477,"description":2478,"path":2479,"category":2032,"date":804,"updatedAt":804,"sourceType":589,"source":2324,"tags":2480},"OpenClaw 工作流治理能力继续成型","官方最近的 ClawHub、Lobster、OpenProse 与 Exec approvals 文档，正在把技能发现、确定性执行和审批恢复串成更完整的一条线。","/news/openclaw-workflow-governance-watch-2026-03-22",[659,1080,860,931,1098],{"title":2482,"description":2483,"path":2484,"category":2485,"date":2486,"updatedAt":2486,"sourceType":609,"source":2487,"tags":2488},"OpenClaw 中文站本周更新：扩展能力地图、案例展示重构与周更内容节奏启动","本周中文站完成扩展目录重排、案例展示页重构，并开始按“教程 + 更新 + 案例”三类节奏持续发布内容。","/news/openclawcn-weekly-update-2026-03-15","站点更新","2026-03-15","openclawcn.xyz",[2489,2490,614,2224,2491],"site-update","content","weekly",{"title":2493,"description":2494,"path":2495,"category":2496,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2497},"OpenClaw 隐私优先：数据保留在本地设备","OpenClaw 强调数据本地存储，用户数据保留在自有设备上，不上传到云端。","/news/privacy-first","产品理念",[997,2498,594,2499],"local-first","data",{"title":2501,"description":2502,"path":2503,"category":1941,"date":1826,"updatedAt":673,"sourceType":1527,"source":1942,"tags":2504},"OpenClaw 项目持续活跃：主仓库星标突破 287k","OpenClaw 开源项目持续快速发展，主仓库星标数突破 287,000，ClawHub 技能目录已收录 349 个开源项目。","/news/project-update-march-2026",[1527,1944,877,1899],{"title":2506,"description":2507,"path":2508,"category":2011,"date":1986,"updatedAt":927,"sourceType":589,"source":1827,"tags":2509},"OpenClaw 2026 年第一季度回顾","回顾 OpenClaw 在 2026 年第一季度的重要更新、社区成长和产品里程碑。","/news/q1-2026-review",[2510,2511,2512,1945],"quarterly","review","2026",{"title":2514,"description":2515,"path":2516,"category":1833,"date":673,"updatedAt":707,"sourceType":589,"source":1827,"tags":2517},"OpenClaw 安全架构深度解析","深入了解 OpenClaw 的安全设计理念、数据保护机制和企业级安全特性。","/news/security-architecture",[594,997,632,624],{"title":2519,"description":2520,"path":2521,"category":2522,"date":673,"updatedAt":673,"sourceType":877,"source":2523,"tags":2524},"OpenClaw 安全最佳实践：保护你的 AI 助手免受风险","随着 OpenClaw 的普及，安全问题日益受到关注。本文整理了保护本地 AI 助手的关键安全措施和最佳实践。","/news/security-best-practices","安全公告","安全社区",[594,997,1376,726],{"title":2526,"description":2527,"path":2528,"category":1904,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2529},"OpenClaw Signal 隐私通讯集成","了解如何将 OpenClaw 连接到 Signal，实现隐私通讯。","/news/signal-privacy",[1157,997,1906,642],{"title":2531,"description":2532,"path":2533,"category":1883,"date":1852,"updatedAt":927,"sourceType":1527,"source":1853,"tags":2534},"OpenClaw 技能市场突破 400 个技能","OpenClaw 技能市场迎来重要里程碑，社区贡献的技能数量突破 400 个，覆盖更多应用场景。","/news/skills-marketplace-400",[626,1945,877,2535],"marketplace",{"title":2537,"description":2538,"path":2539,"category":1904,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2540},"OpenClaw Slack 工作区集成","了解如何将 OpenClaw 集成到 Slack 工作区，实现团队协作。","/news/slack-workspace",[921,762,1906,642],{"title":2542,"description":2543,"path":2544,"category":1844,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2545},"OpenClaw Tailscale 远程访问完全指南","了解如何使用 Tailscale 安全远程访问 OpenClaw，包括 Serve、Funnel 和身份认证。","/news/tailscale-integration",[1278,683,2546,594],"vpn",{"title":2548,"description":2549,"path":2550,"category":1904,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2551},"OpenClaw Telegram Bot 配置指南","了解如何创建和配置 Telegram Bot 连接到 OpenClaw。","/news/telegram-bot",[852,1203,1906,642],{"title":2553,"description":2554,"path":2555,"category":2556,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2557},"OpenClaw 与 VirusTotal 合作推出技能安全验证","OpenClaw 宣布与 VirusTotal 合作，为技能（Skills）提供安全验证服务，确保用户使用安全的 AI 技能。","/news/virustotal-integration","安全更新",[594,2558,626,2559],"virustotal","verification",{"title":2561,"description":2562,"path":2563,"category":1844,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2564},"OpenClaw 语音与 Canvas 功能详解","深入了解 OpenClaw 的语音交互能力和实时 Canvas 可视化功能，如何在日常场景中发挥价值。","/news/voice-and-canvas",[900,1875,1877,2565],"multimodal",{"title":2567,"description":2568,"path":2569,"category":1851,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2570},"OpenClaw iOS 语音唤醒功能正式发布","OpenClaw iOS 应用现已支持语音唤醒功能，用户可以通过\"Hey Siri\"风格的唤醒词激活助手。","/news/voice-wakeup-ios",[1088,900,2571,1391],"wakeup",{"title":2573,"description":2574,"path":2575,"category":1904,"date":1826,"updatedAt":673,"sourceType":589,"source":1827,"tags":2576},"OpenClaw WhatsApp 连接完全指南","详细了解如何将 WhatsApp 连接到 OpenClaw，包括配对、安全配置和常见问题解决。","/news/whatsapp-connection",[853,1906,2577,642],"baileys",{"count":2579,"items":2580},105,[2581,2588,2595,2602,2609,2616,2625,2631,2637,2643,2649,2656,2665,2673,2679,2689,2698,2705,2713,2722,2728,2736,2741,2746,2756,2762,2769,2774,2780,2787,2794,2801,2807,2812,2818,2824,2829,2834,2840,2846,2852,2858,2863,2869,2875,2882,2887,2894,2900,2906,2913,2918,2924,2929,2936,2945,2950,2957,2963,2968,2976,2983,2989,2994,2999,3005,3011,3019,3024,3030,3035,3041,3046,3052,3058,3063,3068,3074,3079,3086,3093,3099,3104,3110,3115,3122,3128,3135,3143,3149,3154,3159,3165,3170,3176,3181,3186,3192,3197,3205,3211,3216,3222,3227,3232],{"title":2582,"description":2583,"path":2584,"category":2585,"difficulty":2586,"updatedAt":681,"sourceType":589,"tags":2587},"管理员常用 CLI 值班手册","结合最新官方 CLI Reference、Gateway protocol 和 Dashboard 文档，总结长期运行环境里管理员最常用的 CLI 值班顺序：先看 status、再看 health、最后进 logs 与 gateway RPC。","/best-practices/admin-cli-playbook","运维实践","初级",[790,1299,633,1034,285],{"title":2589,"description":2590,"path":2591,"category":2592,"difficulty":2586,"updatedAt":673,"sourceType":770,"tags":2593},"AI 提示词工程指南","优化与 AI 助手的交互效果，包括提示词技巧、角色设定和上下文管理。","/best-practices/ai-prompt-engineering","进阶指南",[2594,1195,659,1846],"prompting",{"title":2596,"description":2597,"path":2598,"category":2599,"difficulty":2600,"updatedAt":822,"sourceType":589,"tags":2601},"API 集成面该怎么选：管理、实时还是嵌入式开发","结合最新官方 API、Gateway Web 与 SDK 文档，整理一套更稳的接口面选择方法，帮助团队区分什么时候走 HTTP API、什么时候走 Gateway WebSocket、什么时候用 SDK。","/best-practices/api-surface-selection","开发治理","中高级",[1241,1247,1639,2035,624],{"title":2603,"description":2604,"path":2605,"category":2606,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":2608},"需要审批的自动化流程应该怎么设计","结合最新官方 Lobster、Exec approvals 和 OpenProse 文档，整理一套更稳的自动化设计顺序，让分析、审批和副作用执行分层出现。","/best-practices/approval-gated-automation","自动化治理","高级",[660,931,1080,929,1098],{"title":2610,"description":2611,"path":2612,"category":2613,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2615},"自动化工作流设计","使用 OpenClaw 构建自动化工作流，包括定时任务、事件触发和条件分支。","/best-practices/automation-workflows","自动化","中级",[660,937,1293,973],{"title":2617,"description":2618,"path":2619,"category":2620,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2621},"备份、恢复与灾难恢复","建立完善的备份策略，包括配置备份、数据备份和灾难恢复方案。","/best-practices/backup-recovery","运维管理",[2622,2623,2624,633],"backup","recovery","disaster-recovery",{"title":2626,"description":2627,"path":2628,"category":2629,"difficulty":2607,"updatedAt":822,"sourceType":589,"tags":2630},"Broadcast Groups 上线前，先把多代理协作边界定清楚","结合最新官方 Broadcast Groups 与 Channel Routing 文档，整理多代理同群运行时的角色拆分、工具权限、响应节奏和群入口触发规则，避免把实验能力直接变成高噪声群机器人。","/best-practices/broadcast-group-governance","渠道治理",[824,825,808,1098,807],{"title":2632,"description":2633,"path":2634,"category":2635,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":2636},"浏览器管理员面要按信任链分层开放","结合最新官方 Pairing、Remote Access、Trusted Proxy Auth 和 Dashboard 文档，总结浏览器管理面更稳的开放顺序，避免把地址可达、身份认证、设备配对和 operator 权限混成一个问题。","/best-practices/browser-admin-trust-chain","协作运维",[668,886,20,965,594],{"title":2638,"description":2639,"path":2640,"category":2592,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2641},"浏览器自动化实战","利用 OpenClaw 的浏览器控制能力实现网页自动化，提升工作效率。","/best-practices/browser-automation",[907,660,2642,937],"chromium",{"title":2644,"description":2645,"path":2646,"category":2647,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2648},"Canvas 交互式界面开发","学习使用 A2UI 语法创建交互式 Canvas 界面，包括表单、图表和数据展示。","/best-practices/canvas-interactive","可视化开发",[1875,1876,1878,1877],{"title":2650,"description":2651,"path":2652,"category":2653,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":2654},"用 message CLI 和命令入口时，怎么避免发到错误会话","结合最新官方 Messages、Channel Routing 和 WebChat 文档，整理频道目标、session key、reply routing 和 operator 命令入口之间的关系，避免“命令发对了，结果进错桶”。","/best-practices/channel-command-session-targeting","消息治理",[613,807,2655,826,633],"message-cli",{"title":2657,"description":2658,"path":2659,"category":2660,"difficulty":2614,"updatedAt":927,"sourceType":770,"tags":2661},"OpenClaw 中文优化指南","针对中文用户的 OpenClaw 优化配置，包括模型选择、提示词优化和中文技能推荐。","/best-practices/chinese-optimization","最佳实践",[2662,2663,1886,2664],"chinese","optimization","tips",{"title":2666,"description":2667,"path":2668,"category":2669,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2670},"CI/CD 集成与部署自动化","将 OpenClaw 集成到 CI/CD 流程，实现自动化构建、测试和部署。","/best-practices/ci-cd-integration","开发流程",[2671,1765,2672,660],"ci-cd","testing",{"title":2674,"description":2675,"path":2676,"category":2677,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":2678},"正式配置、环境变量和一次性 override 应该怎么分层","结合最新官方 Configuration、Environment Variables、Logging 和 Debugging 文档，总结长期环境里怎么区分 on-disk config、env 注入、CLI 覆盖和 /debug 一次性改动，避免把临时修复留成永久配置。","/best-practices/config-layering-and-oneoff-overrides","配置治理",[625,1173,2109,1561,633],{"title":2680,"description":2681,"path":2682,"category":2683,"difficulty":2586,"updatedAt":707,"sourceType":877,"tags":2684},"内容创作助手","使用 OpenClaw 构建内容创作工作流，实现写作辅助、翻译、内容优化和多平台发布。","/best-practices/content-creation","内容创作",[2490,2685,2686,2687,2688],"writing","translation","publishing","productivity",{"title":2690,"description":2691,"path":2692,"category":2693,"difficulty":2614,"updatedAt":832,"sourceType":589,"tags":2694},"内容网络编辑手册：把文档、实践、新闻和专题真正织成一套知识体系","面向内容站运营，把文档、最佳实践、新闻动态、专题页和学习路径放到同一张编辑地图里，帮助持续产出更完整、更可回流的长文和系列内容。","/best-practices/content-network-editorial-playbook","内容运营",[2490,2695,2696,701,2697,1376],"seo","editorial","news",{"title":2699,"description":2700,"path":2701,"category":2702,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":2703},"Control UI 安全降级开关应该怎样做 break-glass 管理","结合最新官方安全、Dashboard 和 Control UI 文档，总结 allowInsecureAuth、dangerouslyDisableDeviceAuth 这类降级开关在什么情况下可以临时使用，以及怎样快速回滚。","/best-practices/control-ui-break-glass-policy","安全治理",[886,594,2704,593,623],"break-glass",{"title":2706,"description":2707,"path":2708,"category":2709,"difficulty":2614,"updatedAt":707,"sourceType":589,"tags":2710},"自定义技能开发指南","从零开始开发 OpenClaw 自定义技能，包括项目结构、配置文件、处理逻辑、测试方法和发布流程。","/best-practices/custom-skill-development","开发",[626,2711,2712,642],"development","custom",{"title":2714,"description":2715,"path":2716,"category":2717,"difficulty":2614,"updatedAt":707,"sourceType":877,"tags":2718},"企业客服自动化","使用 OpenClaw 构建智能客服系统，实现自动问答、工单处理、多渠道接入和数据分析。","/best-practices/customer-service-advanced","企业应用",[2719,632,660,2720,2721],"customer-service","chatbot","support",{"title":2723,"description":2724,"path":2725,"category":2726,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2727},"客户服务场景应用","使用 OpenClaw 构建智能客服系统，包括自动回复、工单管理和满意度调查。","/best-practices/customer-service","应用场景",[2719,937,660,2721],{"title":2729,"description":2730,"path":2731,"category":2732,"difficulty":2586,"updatedAt":673,"sourceType":770,"tags":2733},"界面定制与主题","定制 OpenClaw Control UI 的界面和主题。","/best-practices/customization-ui","定制开发",[1878,2734,2735,886],"customization","themes",{"title":2737,"description":2738,"path":2739,"category":2585,"difficulty":2614,"updatedAt":724,"sourceType":589,"tags":2740},"Dashboard 认证引导与 token 漂移该怎么处理","结合最新官方 dashboard CLI 与 Web Dashboard 文档，整理一套更稳的 Dashboard 打开和鉴权恢复顺序，避免把本地、远程、SecretRef token 和浏览器缓存问题混成一个故障。","/best-practices/dashboard-auth-bootstrap-and-drift",[668,593,906,1553,907,633],{"title":2742,"description":2743,"path":2744,"category":2585,"difficulty":2614,"updatedAt":1239,"sourceType":589,"tags":2745},"Dashboard 出现授权漂移时，先走恢复梯子，不要上来就重装","结合最新官方 Dashboard 文档，整理一套更稳的 Dashboard 恢复梯子，把 localhost、远程、SecretRef token、trusted retry 和实例混淆分开排，避免把简单 drift 升级成大修。","/best-practices/dashboard-recovery-ladder",[668,2623,593,2048,633],{"title":2747,"description":2748,"path":2749,"category":2750,"difficulty":2614,"updatedAt":707,"sourceType":877,"tags":2751},"数据分析助手","使用 OpenClaw 构建数据分析助手，实现报表生成、数据可视化、异常检测和智能洞察。","/best-practices/data-analysis-advanced","数据分析",[2752,1877,2753,2754,2755],"data-analysis","reporting","insights","analytics",{"title":2757,"description":2758,"path":2759,"category":2760,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2761},"数据分析与可视化","使用 OpenClaw 进行数据分析，包括数据收集、处理和可视化展示。","/best-practices/data-analysis","数据处理",[2499,1839,1877,937],{"title":2763,"description":2764,"path":2765,"category":2766,"difficulty":2614,"updatedAt":707,"sourceType":877,"tags":2767},"开发者工作流自动化","使用 OpenClaw 构建开发者工作流，实现代码审查、调试辅助、文档生成和 Git 操作自动化。","/best-practices/developer-workflow","开发效率",[1856,2768,1785,660,2688],"code-review",{"title":2770,"description":2771,"path":2772,"category":2702,"difficulty":2614,"updatedAt":822,"sourceType":589,"tags":2773},"设备配对不是一次性批准，应该有定期复核周期","结合最新官方 Devices CLI 与 Pairing 文档，整理浏览器、桌面设备、移动节点和远程 operator 环境里的设备复核节奏，避免已授权设备集合长期失控。","/best-practices/device-pairing-review-cycle",[966,965,2511,1312,2145],{"title":2775,"description":2776,"path":2777,"category":2778,"difficulty":2607,"updatedAt":822,"sourceType":589,"tags":2779},"diagnostics.enabled、flags 和 raw stream 该怎么分层","结合最新官方 Diagnostics Flags、Debugging 与 Raw Stream 文档，整理一套更稳的诊断开关分层方法，避免把定向诊断、全局日志和原始流抓包混成一层。","/best-practices/diagnostics-scope-control","排障实践",[1476,1570,1686,1034,1739],{"title":2781,"description":2782,"path":2783,"category":2784,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2785},"Discord Bot 高级功能开发","深入学习 Discord Bot 的高级功能，包括 Slash 命令、Embed 消息和语音频道集成。","/best-practices/discord-bot-advanced","渠道实践",[854,1203,613,2786],"advanced",{"title":2788,"description":2789,"path":2790,"category":2791,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2792},"Docker 部署与容器化运行","使用 Docker 部署 OpenClaw，包括镜像构建、docker-compose 配置和 Kubernetes 部署。","/best-practices/docker-deployment","部署运维",[1771,1765,2793,633],"containers",{"title":2795,"description":2796,"path":2797,"category":2798,"difficulty":2607,"updatedAt":673,"sourceType":770,"tags":2799},"企业级安全配置","企业环境中的安全配置最佳实践，包括 SSO、审计和合规性。","/best-practices/enterprise-security","企业部署",[632,594,2800,2387],"sso",{"title":2802,"description":2803,"path":2804,"category":2805,"difficulty":2614,"updatedAt":673,"sourceType":877,"tags":2806},"如何高质量反馈 OpenClaw 问题","把自助排查、站内反馈和 GitHub Issues 用在正确阶段，减少无效沟通并提高问题处理效率。","/best-practices/feedback-loop","社区协作",[1529,1528,877,1476],{"title":2808,"description":2809,"path":2810,"category":2784,"difficulty":2614,"updatedAt":620,"sourceType":589,"tags":2811},"飞书 Bot 接入与团队使用实战","结合官方 Feishu/Lark 文档，整理中文团队接入飞书 Bot 时最值得先确认的事项：长连接模式、群聊边界、额度优化和多人协作时的收口方式。","/best-practices/feishu-bot-development",[943,944,1203,613,632],{"title":2813,"description":2814,"path":2815,"category":2816,"difficulty":2614,"updatedAt":1239,"sourceType":589,"tags":2817},"先分清入口职责，再选 Dashboard、WebChat 还是 API","结合最新官方 Dashboard、WebChat、Session 和 API 文档，整理一套更稳的入口选择矩阵，帮助团队在控制面、会话面和集成面之间少走弯路。","/best-practices/gateway-entry-surface-matrix","使用实践",[285,668,739,1241,719],{"title":2819,"description":2820,"path":2821,"category":2822,"difficulty":2614,"updatedAt":681,"sourceType":589,"tags":2823},"群组、私聊与长期记忆的边界怎么守","结合最新官方 Memory 与 Channel Routing 文档，总结 OpenClaw 在群组、私聊、线程和长期记忆之间更稳的边界做法，避免上下文串线和记忆误读。","/best-practices/group-memory-boundaries","协作实践",[615,764,825,997,807],{"title":2825,"description":2826,"path":2827,"category":2629,"difficulty":2614,"updatedAt":822,"sourceType":589,"tags":2828},"群聊入口上线时，先把 mention 触发策略跑稳","结合最新官方 Groups、Group Messages 和 Messages 文档，整理群聊入口从 allowlist、requireMention 到 /activation 的上线顺序，避免把群机器人一接上就变成高噪声、高成本入口。","/best-practices/group-mention-rollout",[825,1625,1459,613,633],{"title":2830,"description":2831,"path":2832,"category":2613,"difficulty":2614,"updatedAt":681,"sourceType":589,"tags":2833},"用 Heartbeat 和 Cron 做低噪音自动化","结合最新官方自动化文档，总结如何用 Heartbeat 承担周期感知、用 Cron 承担精确调度，避免把主会话做成噪音中心。","/best-practices/heartbeat-cron-composition",[660,1292,788,1293,633],{"title":2835,"description":2836,"path":2837,"category":2838,"difficulty":2586,"updatedAt":681,"sourceType":589,"tags":2839},"Hooks、插件和 Skills 的启用顺序怎么排","结合最新官方 Hooks、Plugins、Skills 和 Onboarding 文档，总结第一次扩展 OpenClaw 时怎样安排 hooks、插件与 skills 的启用顺序，降低排障复杂度。","/best-practices/hooks-onboarding-sequence","扩展实践",[718,716,626,667,879],{"title":2841,"description":2842,"path":2843,"category":2844,"difficulty":2614,"updatedAt":707,"sourceType":589,"tags":2845},"Hooks 实战指南","通过实际案例学习 OpenClaw Hooks 的使用，包括消息处理、自动化触发、内容过滤和外部集成。","/best-practices/hooks-practical-guide","实践",[718,660,937,2035],{"title":2847,"description":2848,"path":2849,"category":2850,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":2851},"identityLinks 更适合当成“身份映射表”，而不是联系人备注","结合最新官方 Session、Configuration Reference 和 Security 文档，总结团队里怎样把 identityLinks 当成正式变更对象来维护，避免跨渠道身份映射越配越乱。","/best-practices/identity-links-change-control","会话治理",[1577,826,807,1098,1376],{"title":2853,"description":2854,"path":2855,"category":2856,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2857},"API 集成与二次开发","使用 OpenClaw API 进行二次开发，包括 REST API、WebSocket 和扩展开发。","/best-practices/integration-development","开发指南",[1241,2035,1247,2711],{"title":2859,"description":2860,"path":2861,"category":2592,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2862},"知识库管理","构建和管理 OpenClaw 知识库，包括知识导入、检索和更新。","/best-practices/knowledge-management",[2262,1661,615,2490],{"title":2864,"description":2865,"path":2866,"category":2620,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2867},"日志管理与分析","集中式日志管理、日志分析和日志可视化。","/best-practices/logging-advanced",[1034,2868,1839,633],"observability",{"title":2870,"description":2871,"path":2872,"category":2873,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":2874},"后台维护任务应该怎么分 lane 和保留周期","结合最新官方 Cron、sessions cleanup、doctor 和 Session 文档，总结长期运行时怎样给 isolated cron、main session、session cleanup 和 run logs 设不同的维护节奏。","/best-practices/maintenance-lanes-and-retention","运维治理",[1394,788,764,1285,633],{"title":2876,"description":2877,"path":2878,"category":2879,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":2880},"索引刷新、embedding cache 和 source of truth 更稳的维护方式","结合最新官方 Memory、memory CLI 和 Session 文档，总结团队里怎样区分 memory files、session transcripts 和检索索引三层对象，避免把“检索层”误当成事实层。","/best-practices/memory-index-refresh-and-trust-boundary","记忆治理",[615,1027,1151,2881,1376],"source-of-truth",{"title":2883,"description":2884,"path":2885,"category":2592,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2886},"记忆系统配置与使用","深入了解 OpenClaw 的记忆系统，包括短期记忆、长期记忆和上下文管理。","/best-practices/memory-management",[615,1195,764,772],{"title":2888,"description":2889,"path":2890,"category":2891,"difficulty":2586,"updatedAt":673,"sourceType":770,"tags":2892},"移动端使用指南","在 iOS 和 Android 设备上使用 OpenClaw 的完整指南。","/best-practices/mobile-app-usage","入门指南",[841,1088,1089,2893],"usage",{"title":2895,"description":2896,"path":2897,"category":2898,"difficulty":2614,"updatedAt":681,"sourceType":589,"tags":2899},"移动节点感知能力怎么逐步启用","结合最新官方 nodes、camera、voice wake 和 location 文档，总结 iOS/Android 节点在相机、语音、位置三类能力上怎样渐进启用，避免一开始权限过重。","/best-practices/mobile-node-sensors","设备实践",[841,779,840,1003,900,1004],{"title":2901,"description":2902,"path":2903,"category":2904,"difficulty":2607,"updatedAt":681,"sourceType":589,"tags":2905},"Model Health 与 Auth 监控怎么做","结合最新官方 Models CLI、Auth Monitoring 和 Model Failover 文档，总结长期运行时怎样监控 OAuth 过期、缺失凭据和 profile 轮转问题。","/best-practices/model-auth-monitoring","模型治理",[732,593,1355,1070,1469,633],{"title":2907,"description":2908,"path":2909,"category":2620,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2910},"监控与告警系统","建立完整的监控和告警系统，包括指标收集、告警规则和通知渠道。","/best-practices/monitoring-alerting",[1355,2911,2912,633],"alerting","metrics",{"title":2914,"description":2915,"path":2916,"category":2629,"difficulty":2614,"updatedAt":822,"sourceType":589,"tags":2917},"多账号渠道的 pairing 和 allowFrom 需要分开治理","结合最新官方 Pairing 文档，整理多账号 Telegram、WhatsApp 等渠道下的 pending 审批、allowFrom 文件和账号 scope 的治理顺序，避免默认账号心智把多入口运营带偏。","/best-practices/multi-account-pairing-operations",[965,1505,1506,613,633],{"title":2919,"description":2920,"path":2921,"category":2922,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2923},"多代理路由配置指南","学习配置 OpenClaw 的多代理路由，实现按渠道、用户或内容类型分配不同代理。","/best-practices/multi-agent-routing","代理配置",[807,808,613,625],{"title":2925,"description":2926,"path":2927,"category":2898,"difficulty":2600,"updatedAt":822,"sourceType":589,"tags":2928},"团队里如何渐进启用 node 能力","结合最新官方 Nodes、Pairing、Camera、Location 与 Voice Wake 文档，整理一套更稳的 node 能力启用顺序，避免一开始就把相机、位置和语音一起打开。","/best-practices/node-capability-rollout",[779,1459,840,900,1003,1004],{"title":2930,"description":2931,"path":2932,"category":2620,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":2933},"通知系统配置","配置 OpenClaw 的通知系统，包括邮件、短信、推送和 Webhook 通知。","/best-practices/notification-system",[2934,817,2935,633],"notifications","email",{"title":2937,"description":2938,"path":2939,"category":2940,"difficulty":2614,"updatedAt":2941,"sourceType":589,"tags":2942},"OpenResponses API 接入与第三方集成","把 OpenClaw Gateway 当成 OpenAI 兼容的 API 后端使用，让第三方应用和工具链直接调用你的自托管 Agent 能力。","/best-practices/openresponses-api-integration","集成开发","2026-05-18",[1241,2035,2943,2944,285],"openresponses","openai-compatible",{"title":2946,"description":2947,"path":2948,"category":2635,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":2949},"多人协作时怎么管理 Operator 浏览器入口","结合最新官方 Dashboard、pairing、remote access 和 devices 文档，总结团队在浏览器 Control UI、多 operator 接力和值班环境里最需要的使用纪律。","/best-practices/operator-browser-discipline",[1404,668,907,965,623],{"title":2951,"description":2952,"path":2953,"category":2954,"difficulty":2614,"updatedAt":1239,"sourceType":589,"tags":2955},"多个 operator 轮流进 Dashboard 时，浏览器交接不要靠记忆","结合最新官方 Dashboard、Control UI 和设备 pairing 文档，整理团队里多个 operator 轮流接管浏览器控制面的交接顺序，避免把 gateway URL、token 来源和已配对浏览器状态混成口口相传的经验。","/best-practices/operator-browser-handoff","协作治理",[1404,668,907,965,2956],"handoff",{"title":2958,"description":2959,"path":2960,"category":2961,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":2962},"operator 入口更稳的升级梯子：先看 UI，再下沉协议和 API","结合最新官方 Dashboard、WebChat、Gateway Protocol 和 API 文档，总结 operator 在排障和协作时怎样按层使用 Dashboard、WebChat、Gateway WebSocket 和 HTTP API，避免一上来就切到过深入口。","/best-practices/operator-surface-escalation-ladder","运维协作",[1404,668,739,1241,937,1376],{"title":2964,"description":2965,"path":2966,"category":2702,"difficulty":2607,"updatedAt":724,"sourceType":589,"tags":2967},"团队里如何做 per-agent 执行白名单治理","结合最新官方 approvals CLI 与 Exec Approvals 文档，整理一套更稳的 per-agent allowlist 管理方法，避免一个 agent 的执行权限外溢到整个团队。","/best-practices/per-agent-allowlist-governance",[931,1051,929,594,1098],{"title":2969,"description":2970,"path":2971,"category":2972,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":2973},"性能优化与监控","优化 OpenClaw 性能，包括缓存策略、资源管理和监控配置。","/best-practices/performance-tuning","运维优化",[1989,2974,2975,1355],"tuning","caching",{"title":2977,"description":2978,"path":2979,"category":2726,"difficulty":2614,"updatedAt":927,"sourceType":770,"tags":2980},"个人知识管理助手","使用 OpenClaw 构建个人知识管理系统，实现笔记整理、知识检索和智能问答。","/best-practices/personal-knowledge-assistant",[2981,2982,691,2688],"knowledge-management","notes",{"title":2984,"description":2985,"path":2986,"category":2987,"difficulty":2607,"updatedAt":681,"sourceType":589,"tags":2988},"团队里如何管理插件包和 Hook Pack","结合最新官方插件与 hooks 文档，总结团队在使用 package pack、hook pack 和插件托管 hooks 时，怎样降低升级、冲突和安全成本。","/best-practices/plugin-bundle-governance","扩展治理",[716,718,1098,623,633],{"title":2990,"description":2991,"path":2992,"category":2987,"difficulty":2607,"updatedAt":724,"sourceType":589,"tags":2993},"插件更新轨道和卸载回收应该怎么安排","结合最新官方 plugins CLI 文档，整理一套更稳的插件生命周期治理方法，帮助团队管理 install spec、update track、卸载回收以及 memory slot 回退行为。","/best-practices/plugin-lifecycle-governance",[716,972,1393,1791,1098],{"title":2995,"description":2996,"path":2997,"category":2635,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":2998},"团队长期运行蓝图：把 OpenClaw 从可用做成可运营","把控制面、渠道、模型、记忆、自动化、安全和维护整合成一套长期运行蓝图，帮助团队把 OpenClaw 从“能跑”推进到“能稳定运营”。","/best-practices/production-operations-blueprint",[633,623,594,798,660,1394],{"title":3000,"description":3001,"path":3002,"category":3003,"difficulty":2607,"updatedAt":724,"sourceType":589,"tags":3004},"从 Prose 准备到 Lobster 执行，交接线怎么画","结合最新官方 Lobster 文档，整理一套从多智能体准备到确定性执行的交接方法，避免 OpenProse 和 Lobster 混层使用。","/best-practices/prose-to-lobster-handoff","工作流实践",[1079,1080,659,931,717],{"title":3006,"description":3007,"path":3008,"category":3009,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":3010},"团队里怎么分层放开 provider、模型和 node 能力","结合最新官方 Models、Model Failover 和 node 文档，总结团队环境里怎样把 provider auth、模型 allowlist、图片能力和远程 node 执行分成不同放开层级，避免一开始给太大权限面。","/best-practices/provider-and-node-capability-lanes","权限与治理",[798,732,779,931,1098,1376],{"title":3012,"description":3013,"path":3014,"category":2904,"difficulty":2607,"updatedAt":681,"sourceType":589,"tags":3015},"团队里如何给 Provider 加统一网关层","结合最新官方 providers、LiteLLM 和 Cloudflare AI Gateway 文档，总结长期运行时怎样把上游模型与统一网关分层，兼顾成本、回退和可观测性。","/best-practices/provider-gateway-layering",[798,3016,3017,3018,807,633],"gateways","litellm","cloudflare",{"title":3020,"description":3021,"path":3022,"category":2904,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":3023},"Provider 故障时先按恢复阶梯排，不要直接乱切模型","结合最新官方 Model Failover、Gateway Troubleshooting、LiteLLM 和 Cloudflare AI Gateway 文档，总结模型调用异常时更稳的恢复顺序，避免把长上下文、认证轮转、网关鉴权和跨模型 fallback 混成一件事。","/best-practices/provider-recovery-ladder",[798,1469,2623,732,633],{"title":3025,"description":3026,"path":3027,"category":3028,"difficulty":2586,"updatedAt":673,"sourceType":589,"tags":3029},"版本升级与内容运营节奏","如何持续跟踪 OpenClaw 的版本变化，并建立稳定的内容运营节奏。","/best-practices/publishing-rhythm","更新跟踪",[1391,1393,659,1394],{"title":3031,"description":3032,"path":3033,"category":2613,"difficulty":2614,"updatedAt":832,"sourceType":589,"tags":3034},"用 quiet hours 和 manual wake 控制自动化节奏","结合最新官方 Heartbeat 与 Automation Troubleshooting 文档，总结如何让 heartbeat 在该安静时安静、在需要时再手动唤醒，避免把自动化做成全天噪音源。","/best-practices/quiet-hours-and-manual-wake",[1292,1632,660,633,1376],{"title":3036,"description":3037,"path":3038,"category":2585,"difficulty":3039,"updatedAt":620,"sourceType":589,"tags":3040},"把版本观察变成升级决策，而不是看见更新就立刻替换环境","结合最新 release 观察、配置变化和迁移信号，建立一套更稳的升级判断顺序：先看影响层，再看风险，再决定是否马上升级。","/best-practices/release-watch-to-upgrade-decision","基础",[1391,1811,1810,633,1392],{"title":3042,"description":3043,"path":3044,"category":2873,"difficulty":2607,"updatedAt":724,"sourceType":589,"tags":3045},"远程值守时如何设计聊天审批路由","结合最新官方 Exec Approvals 与 Remote Operators 文档，整理一套更稳的远程审批路由设计，避免把远程值守便利性直接变成高权限扩散。","/best-practices/remote-approval-routing",[931,683,852,854,1404,807],{"title":3047,"description":3048,"path":3049,"category":2726,"difficulty":2586,"updatedAt":673,"sourceType":770,"tags":3050},"远程工作场景应用","使用 OpenClaw 支持远程工作场景，包括分布式团队协作和远程办公。","/best-practices/remote-work",[3051,947,2688,623],"remote-work",{"title":3053,"description":3054,"path":3055,"category":3056,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":3057},"从巡检到修复的排障阶梯应该怎么走","结合最新官方 Doctor、Diagnostics Flags、Debugging 和 Troubleshooting 文档，总结一条更稳的 repair ladder，让 status、doctor、flags、repair 和 cleanup 各司其职。","/best-practices/repair-ladder-playbook","排障治理",[1318,1476,1739,1319,633],{"title":3059,"description":3060,"path":3061,"category":3056,"difficulty":2614,"updatedAt":681,"sourceType":589,"tags":3062},"Raw Stream 调试的安全做法","结合最新官方 Debugging 文档，总结在 OpenClaw 里抓 raw stream、provider chunk 和诊断日志时，怎样控制范围、保留最小样本并避免泄露 prompt、密钥和用户数据。","/best-practices/safe-debug-capture",[1561,1569,997,594,1739],{"title":3064,"description":3065,"path":3066,"category":2702,"difficulty":2607,"updatedAt":822,"sourceType":589,"tags":3067},"Secret rotation 和 active snapshot 应该怎么配合","结合最新官方 Secrets Management 文档，整理一套更稳的密钥轮换方法，帮助团队理解 SecretRef eager resolve、active snapshot 和 reload 失败时的 last-known-good 边界。","/best-practices/secret-rotation-with-active-snapshot",[1707,1706,2368,2367,633],{"title":3069,"description":3070,"path":3071,"category":2702,"difficulty":2614,"updatedAt":2941,"sourceType":589,"tags":3072},"Secrets 管理与生产环境密钥安全","从官方 Secrets Management 文档出发，整理一套适合生产环境的密钥管理方法，涵盖 SecretRef、运行时快照、provider 配置和常见排障思路。","/best-practices/secrets-management-production",[1706,594,3073,1707,633],"production",{"title":3075,"description":3076,"path":3077,"category":2702,"difficulty":2614,"updatedAt":822,"sourceType":589,"tags":3078},"共享 DM 入口上线前的 secure DM 检查清单","结合最新官方 Session、Security 和 CLI Security 文档，整理共享 DM、配对审批、多账号入口和跨渠道身份映射的上线前核查清单，避免把单人默认配置直接带进多人环境。","/best-practices/secure-dm-rollout-checklist",[594,1576,965,826,1459],{"title":3080,"description":3081,"path":3082,"category":3083,"difficulty":2607,"updatedAt":673,"sourceType":770,"tags":3084},"OpenClaw 安全加固指南","生产环境中 OpenClaw 的安全加固最佳实践，包括认证、授权和网络配置。","/best-practices/security-hardening","安全配置",[594,1414,593,3085],"networking",{"title":3087,"description":3088,"path":3089,"category":3090,"difficulty":2607,"updatedAt":804,"sourceType":589,"tags":3091},"长期使用时 session reset 策略怎么定","结合最新官方会话管理文档，整理 daily reset、idle reset、resetByType、resetByChannel 和 resetTriggers 的组合思路，让长期使用既不失连续性，也不把上下文拖到失控。","/best-practices/session-reset-policy","长期治理",[826,3092,2115,623,633],"reset",{"title":3094,"description":3095,"path":3096,"category":3097,"difficulty":2607,"updatedAt":832,"sourceType":589,"tags":3098},"共享群入口更稳的放开顺序：allowlist、mention、activation 和 broadcast","结合最新官方 Groups、Group Messages 和 Broadcast Groups 文档，总结团队在群聊里怎样从最窄入口逐步放开到 topic、多 agent 和 always activation，避免一开始就把共享群入口做成高噪音面。","/best-practices/shared-group-entry-rollout","群入口治理",[825,1698,2211,824,1098,1376],{"title":3100,"description":3101,"path":3102,"category":2702,"difficulty":2607,"updatedAt":822,"sourceType":589,"tags":3103},"shared inbox 能共用入口，但不要共用不该共用的边界","结合最新官方 Security 与 Groups 文档，整理 shared inbox 场景下 operator、工具、宿主文件系统和私有身份的分层建议，避免把协作入口误用成弱隔离的多租户平台。","/best-practices/shared-inbox-operator-separation",[1428,594,2412,1404,1098],{"title":3105,"description":3106,"path":3107,"category":3108,"difficulty":2607,"updatedAt":673,"sourceType":770,"tags":3109},"技能开发进阶：Hook 与事件处理","学习 OpenClaw 技能系统的高级用法，包括 Hook、事件监听和自定义工作流。","/best-practices/skill-development-advanced","技能开发",[626,718,973,2786],{"title":3111,"description":3112,"path":3113,"category":2592,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":3114},"技能开发指南","深入了解 OpenClaw 技能系统，学习如何开发和自定义专属技能。","/best-practices/skills-development",[626,2711,2734,614],{"title":3116,"description":3117,"path":3118,"category":2726,"difficulty":2614,"updatedAt":927,"sourceType":770,"tags":3119},"OpenClaw 家庭自动化应用","使用 OpenClaw 构建智能家居控制中心，实现语音控制、自动化场景和设备管理。","/best-practices/smart-home-automation",[3120,660,2225,3121],"smart-home","iot",{"title":3123,"description":3124,"path":3125,"category":2922,"difficulty":3039,"updatedAt":2941,"sourceType":589,"tags":3126},"SOUL.md 人格与身份定制实战指南","从官方 SOUL.md 机制出发，教你怎么给 Agent 写一个真正有“性格”而不是“说明书”的身份文件，避免常见的人格配置误区。","/best-practices/soul-personality-guide",[772,3127,612,1194,2734],"personality",{"title":3129,"description":3130,"path":3131,"category":3132,"difficulty":2614,"updatedAt":681,"sourceType":589,"tags":3133},"升级窗口怎么安排更稳","结合最新官方 Install、Updating、Migration 和 Release 文档，总结长期运行时怎样安排 OpenClaw 的升级窗口、验证顺序和回滚边界，避免把升级变成线上事故。","/best-practices/staged-upgrade-windows","维护实践",[1811,1810,1391,1394,3134],"rollback",{"title":3136,"description":3137,"path":3138,"category":3139,"difficulty":2607,"updatedAt":2941,"sourceType":589,"tags":3140},"Sub-agents 子代理工作流与任务拆分","学习如何把复杂任务拆给多个子代理处理，让 OpenClaw 的主 Agent 变成任务调度器而不是所有事都自己干。","/best-practices/sub-agents-workflow","高级用法",[3141,659,717,3142,787],"sub-agents","delegation",{"title":3144,"description":3145,"path":3146,"category":3147,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":3148},"团队协作与工作区管理","配置团队工作区，实现多用户协作、权限管理和团队知识共享。","/best-practices/team-collaboration","团队协作",[623,762,1004,947],{"title":3150,"description":3151,"path":3152,"category":2954,"difficulty":2607,"updatedAt":681,"sourceType":589,"tags":3153},"团队里如何管理 Gateway、Operator 与浏览器控制面","结合最新官方 remote、Control UI、pairing 和 security 文档，总结团队环境里怎样定义主 Gateway、operator 设备和浏览器控制面，降低多人协作时的运维混乱。","/best-practices/team-gateway-operator-playbook",[285,1404,886,965,623,633],{"title":3155,"description":3156,"path":3157,"category":2784,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":3158},"Telegram Bot 开发进阶指南","深入学习 Telegram Bot 的高级功能，包括自定义键盘、Inline 模式和群组管理。","/best-practices/telegram-bot-development",[852,1203,613,2786],{"title":3160,"description":3161,"path":3162,"category":2669,"difficulty":2600,"updatedAt":673,"sourceType":770,"tags":3163},"测试策略与质量保障","建立 OpenClaw 的测试策略，包括单元测试、集成测试和端到端测试。","/best-practices/testing-strategies",[2672,3164,2035,659],"quality",{"title":3166,"description":3167,"path":3168,"category":2873,"difficulty":2614,"updatedAt":2941,"sourceType":589,"tags":3169},"Transcript 会话记录治理与归档策略","结合官方 Transcript Hygiene 文档，整理一套会话记录的治理方法，帮助长期运行的 OpenClaw 实例控制存储增长、保障隐私合规。","/best-practices/transcript-hygiene-governance",[1719,764,1745,997,2387,633],{"title":3171,"description":3172,"path":3173,"category":3174,"difficulty":2607,"updatedAt":673,"sourceType":770,"tags":3175},"高级故障排除与诊断","深入排查 OpenClaw 复杂问题，包括性能问题、渠道故障和系统崩溃。","/best-practices/troubleshooting-advanced","故障排除",[1739,1476,1989,613],{"title":3177,"description":3178,"path":3179,"category":2702,"difficulty":2607,"updatedAt":724,"sourceType":589,"tags":3180},"Trusted Proxy 上线前应该过哪些检查","结合最新官方 trusted-proxy auth 与 security audit 文档，整理一套上线前检查顺序，避免把只是做 TLS 的反向代理误当成可托付身份的安全代理。","/best-practices/trusted-proxy-rollout-checklist",[20,592,593,594,1459],{"title":3182,"description":3183,"path":3184,"category":2585,"difficulty":2614,"updatedAt":1239,"sourceType":589,"tags":3185},"UI 和 API 看到的状态对不上时，先查哪一层","结合最新官方 Session、WebChat 和 API 文档，整理一套更稳的排障顺序，帮助团队区分 Gateway 事实层、UI 投影视图和结构化接口之间的差异。","/best-practices/ui-vs-api-state-debugging",[285,739,1241,1561,826],{"title":3187,"description":3188,"path":3189,"category":2873,"difficulty":2607,"updatedAt":724,"sourceType":589,"tags":3190},"团队里如何给 stable、beta、dev 分层","结合最新官方 update CLI 与 Updating 文档，整理一套更稳的更新分层策略，帮助团队把 stable、beta、dev 变成有职责分工的 rollout 体系。","/best-practices/update-channel-staging",[1455,1456,1457,1458,3191,1459],"staging",{"title":3193,"description":3194,"path":3195,"category":2620,"difficulty":2614,"updatedAt":673,"sourceType":589,"tags":3196},"版本升级与迁移","OpenClaw 版本升级步骤、迁移指南和回滚方案。","/best-practices/upgrade-migration",[1811,1810,3134,1394],{"title":3198,"description":3199,"path":3200,"category":3201,"difficulty":2586,"updatedAt":673,"sourceType":770,"tags":3202},"语音助手配置与使用指南","全面了解 OpenClaw 语音功能的配置和使用，包括语音唤醒、连续对话和语音合成。","/best-practices/voice-assistant-setup","语音交互",[900,3203,3204,676],"wakeword","speech",{"title":3206,"description":3207,"path":3208,"category":3209,"difficulty":2586,"updatedAt":673,"sourceType":770,"tags":3210},"语音功能最佳实践","如何在日常场景中高效使用 OpenClaw 的语音功能，提升工作和生活效率。","/best-practices/voice-usage","使用技巧",[900,2893,2688,710],{"title":3212,"description":3213,"path":3214,"category":2816,"difficulty":2586,"updatedAt":681,"sourceType":589,"tags":3215},"Web 入口怎么选：Dashboard、WebChat、message CLI","结合最新官方 Dashboard、WebChat 和 CLI 文档，总结什么时候该用 Dashboard、什么时候用 WebChat、什么时候更适合用 openclaw message 做验证与自动化。","/best-practices/web-entry-selection",[668,739,790,2132,937],{"title":3217,"description":3218,"path":3219,"category":2816,"difficulty":2614,"updatedAt":724,"sourceType":589,"tags":3220},"WebChat 更适合当什么，不适合当什么","结合最新官方 WebChat 文档，整理一套更稳的 WebChat 使用策略，帮助团队把它作为 operator 和验证入口，而不是过早承担所有长期协作场景。","/best-practices/webchat-operator-usage-policy",[739,668,3221,807,937],"operator",{"title":3223,"description":3224,"path":3225,"category":2613,"difficulty":2614,"updatedAt":681,"sourceType":589,"tags":3226},"用 Webhooks 做安全的外部事件接入","结合最新官方 Webhooks 文档，总结如何把 Gmail、表单、工单和内部系统事件安全送进 OpenClaw，同时避免会话污染和误投递。","/best-practices/webhook-ingest-routing",[1255,718,660,1256,594],{"title":3228,"description":3229,"path":3230,"category":2693,"difficulty":3039,"updatedAt":2486,"sourceType":609,"tags":3231},"用 OpenClaw 搭建每周“教程 + 更新 + 案例”内容流水线","把教程、版本更新和案例拆成固定节奏，用一套低成本流程持续为中文站带来搜索流量、时效内容和转化素材。","/best-practices/weekly-content-pipeline",[2490,2687,659,2695,2491],{"title":3233,"description":3234,"path":3235,"category":2784,"difficulty":2614,"updatedAt":673,"sourceType":770,"tags":3236},"WhatsApp 自动化工作流实战","利用 OpenClaw 的 WhatsApp 渠道实现自动化工作流，包括自动回复、消息转发和定时提醒。","/best-practices/whatsapp-automation",[853,660,613,659],{"all":3238,"docs":601,"news":1819,"bestPractices":2579},392,1792394217096]