[{"data":1,"prerenderedAt":243},["ShallowReactive",2],{"page-/post/tech-news/openclaw-v2026-2-19":3,"surrounding-page":234},{"id":4,"title":5,"author":6,"body":7,"date":216,"description":217,"extension":218,"group":219,"lastmod":216,"meta":220,"navigation":222,"path":223,"rawbody":224,"seo":225,"showTitle":219,"stem":226,"tags":227,"versions":219,"__hash__":233},"content/post/tech-news/openclaw-v2026-2-19.md","OpenClaw v2026.2.19：Apple Watch companion、设备移除流程，以及「无鉴权 HTTP」审计提醒","Jinx",{"type":8,"value":9,"toc":207},"minimark",[10,19,34,46,51,58,77,80,84,87,105,108,111,115,118,133,141,148,152,155,158,162,165,180,183,204],[11,12,13,14,18],"p",{},"中午刷到 OpenClaw 的 release：",[15,16,17],"strong",{},"v2026.2.19","。",[11,20,21,22,25,26,29,30,33],{},"本以为就是常规“加功能 + 修 bug”，结果这版的点还挺明确：",[15,23,24],{},"把「随身收件箱」做到了 Apple Watch 上","，同时也把",[15,27,28],{},"设备生命周期管理","和",[15,31,32],{},"安全风险提示","补得更完整。",[35,36,37],"blockquote",{},[11,38,39,40],{},"来源（Release Notes）：",[41,42,43],"a",{"href":43,"rel":44},"https://github.com/openclaw/openclaw/releases/tag/v2026.2.19",[45],"nofollow",[47,48,50],"h2",{"id":49},"apple-watch-companion-mvp手表上也能看-inbox-通知","Apple Watch companion MVP：手表上也能看 inbox / 通知",[11,52,53,54,57],{},"Release notes 里提到的是一个 ",[15,55,56],{},"companion MVP","，重点包括：",[59,60,61,68,74],"ul",{},[62,63,64,65],"li",{},"Watch 端的 ",[15,66,67],{},"inbox UI",[62,69,70,73],{},[15,71,72],{},"通知中继","（你可以理解为：把关键提醒更“贴身”地送到手表上）",[62,75,76],{},"以及和 gateway command 相关的面板/入口（MVP 级别）",[11,78,79],{},"我个人的感受是：很多自动化工具最后拼的不是功能，而是“你有没有真的看到它”。\n手表这种入口，反而特别适合接「只看一眼就要做决定」的提醒。",[47,81,83],{"id":82},"gatewaycli新增配对设备移除清理流程终于能体面地删设备了","Gateway/CLI：新增配对设备移除/清理流程（终于能体面地删设备了）",[11,85,86],{},"这版补了设备清理/移除的完整流程，release notes 里列的命令/端点包括：",[59,88,89,95,100],{},[62,90,91],{},[92,93,94],"code",{},"device.pair.remove",[62,96,97],{},[92,98,99],{},"openclaw devices remove",[62,101,102],{},[92,103,104],{},"openclaw devices clear --yes [--pending]",[11,106,107],{},"以前很多系统的“配对”做得挺顺，但“解绑/清理”反而模糊：\n设备换机、测试机报废、或者 pending 一堆卡着……最后就是一团乱麻。",[11,109,110],{},"这类功能不性感，但真的省心。",[47,112,114],{"id":113},"securityaudit当-gatewayauthmodenone-时新增gatewayhttpno_auth审计发现","Security/Audit：当 gateway.auth.mode=\"none\" 时，新增「gateway.http.no_auth」审计发现",[11,116,117],{},"我觉得这条属于“该提醒就得提醒”。",[11,119,120,121,124,125,128,129,132],{},"release notes 说：当你把 ",[92,122,123],{},"gateway.auth.mode=\"none\""," 打开，导致 ",[15,126,127],{},"HTTP API 可达","时，会新增一个审计发现：",[92,130,131],{},"gateway.http.no_auth","。\n并且会区分：",[59,134,135,138],{},[62,136,137],{},"loopback（只在本机）情况下的警告",[62,139,140],{},"远程暴露情况下更严重的级别提示",[11,142,143,144,147],{},"一句话：",[15,145,146],{},"你可以为了方便临时不开鉴权，但系统会明确告诉你这事有多危险","。\n（不然真有人一不小心把接口暴露到公网，然后就不是“翻车”，是“被拆家”。）",[47,149,151],{"id":150},"telegramcronheartbeat修复-topic-目标投递定时任务更稳","Telegram/Cron/Heartbeat：修复 topic 目标投递，定时任务更稳",[11,153,154],{},"这条也很实用：修复了 Telegram 的 topic 目标投递，确保 cron 按配置的 topic 发送。",[11,156,157],{},"这种问题特别烦：你以为自己配置错了，折腾半小时，最后发现是投递链路本身的 bug。\n修了就好。",[47,159,161],{"id":160},"我会怎么升级偏向建议升级","我会怎么升级（偏向建议升级）",[11,163,164],{},"如果你现在在用 OpenClaw，我会偏向建议升级到这版，理由很简单：",[59,166,167,174],{},[62,168,169,170,173],{},"有",[15,171,172],{},"安全审计提醒","（降低“无意裸奔”概率）",[62,175,169,176,179],{},[15,177,178],{},"cron/投递修复","（减少关键提醒丢失/发错地方）",[11,181,182],{},"但我也会按老规矩来：",[184,185,186,189],"ol",{},[62,187,188],{},"先在测试机/非关键通道升级",[62,190,191,192],{},"专门回归两件事：\n",[59,193,194,197],{},[62,195,196],{},"Telegram topic + cron 的投递是否符合预期",[62,198,199,200,203],{},"设备移除/clear 是否会误伤（尤其是 ",[92,201,202],{},"--pending"," 的行为）",[11,205,206],{},"不行就回滚。\n稳一点。",{"title":208,"searchDepth":209,"depth":209,"links":210},"",2,[211,212,213,214,215],{"id":49,"depth":209,"text":50},{"id":82,"depth":209,"text":83},{"id":113,"depth":209,"text":114},{"id":150,"depth":209,"text":151},{"id":160,"depth":209,"text":161},"2026-02-21T04:00:00.000Z","这版我最想提三件事：Apple Watch companion MVP、配对设备的移除/清理流程、以及当 gateway 以 no-auth 暴露 HTTP API 时的安全审计发现。","md",null,{"category":221},"技术",true,"/post/tech-news/openclaw-v2026-2-19","---\ntitle: OpenClaw v2026.2.19：Apple Watch companion、设备移除流程，以及「无鉴权 HTTP」审计提醒\ndescription: 这版我最想提三件事：Apple Watch companion MVP、配对设备的移除/清理流程、以及当 gateway 以 no-auth 暴露 HTTP API 时的安全审计发现。\nauthor: Jinx\ndate: \"2026-02-21T12:00:00+08:00\"\nlastmod: \"2026-02-21T12:00:00+08:00\"\ntags: [\"OpenClaw\", \"Apple Watch\", \"Security\", \"CLI\", \"Release Notes\"]\ncategory: 技术\n---\n\n中午刷到 OpenClaw 的 release：**v2026.2.19**。\n\n本以为就是常规“加功能 + 修 bug”，结果这版的点还挺明确：**把「随身收件箱」做到了 Apple Watch 上**，同时也把**设备生命周期管理**和**安全风险提示**补得更完整。\n\n> 来源（Release Notes）：https://github.com/openclaw/openclaw/releases/tag/v2026.2.19\n\n## Apple Watch companion MVP：手表上也能看 inbox / 通知\n\nRelease notes 里提到的是一个 **companion MVP**，重点包括：\n\n- Watch 端的 **inbox UI**\n- **通知中继**（你可以理解为：把关键提醒更“贴身”地送到手表上）\n- 以及和 gateway command 相关的面板/入口（MVP 级别）\n\n我个人的感受是：很多自动化工具最后拼的不是功能，而是“你有没有真的看到它”。\n手表这种入口，反而特别适合接「只看一眼就要做决定」的提醒。\n\n## Gateway/CLI：新增配对设备移除/清理流程（终于能体面地删设备了）\n\n这版补了设备清理/移除的完整流程，release notes 里列的命令/端点包括：\n\n- `device.pair.remove`\n- `openclaw devices remove`\n- `openclaw devices clear --yes [--pending]`\n\n以前很多系统的“配对”做得挺顺，但“解绑/清理”反而模糊：\n设备换机、测试机报废、或者 pending 一堆卡着……最后就是一团乱麻。\n\n这类功能不性感，但真的省心。\n\n## Security/Audit：当 gateway.auth.mode=\"none\" 时，新增「gateway.http.no_auth」审计发现\n\n我觉得这条属于“该提醒就得提醒”。\n\nrelease notes 说：当你把 `gateway.auth.mode=\"none\"` 打开，导致 **HTTP API 可达**时，会新增一个审计发现：`gateway.http.no_auth`。\n并且会区分：\n\n- loopback（只在本机）情况下的警告\n- 远程暴露情况下更严重的级别提示\n\n一句话：**你可以为了方便临时不开鉴权，但系统会明确告诉你这事有多危险**。\n（不然真有人一不小心把接口暴露到公网，然后就不是“翻车”，是“被拆家”。）\n\n## Telegram/Cron/Heartbeat：修复 topic 目标投递，定时任务更稳\n\n这条也很实用：修复了 Telegram 的 topic 目标投递，确保 cron 按配置的 topic 发送。\n\n这种问题特别烦：你以为自己配置错了，折腾半小时，最后发现是投递链路本身的 bug。\n修了就好。\n\n## 我会怎么升级（偏向建议升级）\n\n如果你现在在用 OpenClaw，我会偏向建议升级到这版，理由很简单：\n\n- 有**安全审计提醒**（降低“无意裸奔”概率）\n- 有**cron/投递修复**（减少关键提醒丢失/发错地方）\n\n但我也会按老规矩来：\n\n1. 先在测试机/非关键通道升级\n2. 专门回归两件事：\n   - Telegram topic + cron 的投递是否符合预期\n   - 设备移除/clear 是否会误伤（尤其是 `--pending` 的行为）\n\n不行就回滚。\n稳一点。\n",{"title":5,"description":217},"post/tech-news/openclaw-v2026-2-19",[228,229,230,231,232],"OpenClaw","Apple Watch","Security","CLI","Release Notes","xv4cP9YenDvbXqz35CHtKcAiwJ7smmG-b4WNv1IBNpw",[235,239],{"title":236,"path":237,"stem":238,"children":-1},"OpenClaw 安装入门（Windows）","/post/zzao/openclaw/openclaw-install-windows","post/zzao/openclaw/openclaw-install-windows",{"title":240,"path":241,"stem":242,"children":-1},"假设你是AI，你的Skill应该是什么样的","/post/zzao/ai-skill-structure","post/zzao/ai-skill-structure",1779005084793]