2026-07-20 每日新聞檔案

今天建議先抓五個工程點：OpenClaw 用 beta.3 release 把 host ownership、setup 持久化與 recovery path 放進同一張圖，再用 workspace-scoped recommendations 補上狀態作用域；Hermes 則用 production benchmark 與 Kimi adaptive thinking 提醒你把效能量測和 provider 契約分開驗證；外部對照用 TechCrunch 的 Kimi 報導，練習分辨市場敘事與可驗證 API 行為。

封存時間：2026-07-20 07:00 CST

中文 5 條

先讀 release 與 state-scope，再用 benchmark、provider 契約與外部報導練習把同一天的不同敘事改寫成工程驗證表。

回到今日新聞頁
  1. OpenClaw v2026.7.2-beta.3 把 remote coding sessions、cloud workers、guided setup 與 gateway/session recovery 收進同一版，今天最適合拿來教學生把「控制權在哪台主機、哪些步驟會持久化、故障後怎麼續跑」畫成同一張系統圖。
    來源：查看來源（OpenClaw 官方 Release）
  2. OpenClaw 把 onboarding recommendations 改成 workspace-scoped，這是一個很好的狀態主權教材：若建議清單沒有跟 workspace 綁定，使用者很容易把別處的狀態誤當成目前環境的 source of truth。
    來源：查看來源（OpenClaw 官方 Commit）
  3. Hermes 用 production build、cold start 與 first token 重新量 desktop benchmark，這很適合教學生：效能驗證不能只看 dev mode，FCP、TTFT 與 transcript mount 要分開量，才知道真正拖慢互動的是哪一層。
    來源：查看來源（Hermes Agent 官方 Commit）
  4. Hermes 重新替 Kimi-family Anthropic endpoints 打開 adaptive thinking 契約，讓 thinking blocks 與 effort map 可用；這很適合教 API 相容不等於行為相容，真正要驗的是參數契約、回放驗證與 provider-specific fallback。
    來源：查看來源（Hermes Agent 官方 Commit）
  5. TechCrunch 以「Kimi: Threat or menace?」整理 Moonshot AI 新版 Kimi 帶來的競爭壓力，適合當今天的外部對照：同樣是 Kimi，新聞談產品與市場敘事，官方 commit 談 endpoint 契約與推理 effort，學生要學會把兩種敘事拆開。
    來源：查看來源（TechCrunch）

English 5 Items

Use the English list to compare lifecycle ownership, workspace state, production benchmarking, provider contracts, and outside market framing.

查看本月檔案
  1. OpenClaw v2026.7.2-beta.3 bundles remote coding sessions, cloud workers, guided setup, and gateway/session recovery into one release, making it today's clearest official lesson in host ownership, state persistence, and resume paths.
    Source: Source (OpenClaw Official Release)
  2. OpenClaw scopes onboarding recommendations by workspace, a compact state-ownership lesson: if recommendation state is not tied to the active workspace, users can mistake another environment's hints for the current source of truth.
    Source: Source (OpenClaw Official Commit)
  3. Hermes reworks desktop benchmarking around production builds, cold-start, and first-token latency, a strong lesson that performance work cannot stop at dev mode numbers: FCP, TTFT, and transcript mount must be measured separately.
    Source: Source (Hermes Agent Official Commit)
  4. Hermes restores adaptive thinking for Kimi-family Anthropic endpoints, making it a clean lesson that API compatibility is not behavioral compatibility: the real work is in parameter contracts, replay validation, and provider-specific fallback.
    Source: Source (Hermes Agent Official Commit)
  5. TechCrunch's “Kimi: Threat or menace?” frames Moonshot AI's latest Kimi push as a competitive story, giving today's outside comparison point: media narratives about product pressure should be separated from the endpoint contract details that official commits actually verify.
    Source: Source (TechCrunch)