OpenClaw tagged stable v2026.11.2 on GitHub (published 2026-11-08T19:31:04Z = Mon 2026-11-09 03:31 HKT) — soft title: platforms / agent-runtime privacy + update-recovery, not a new model and not a Multiplayer or catalog-blog re-card (Multiplayer / v2026.11.1 already Fri LIVE). Official highlights: keep configuration secrets, conversation content, tool errors, and channel payloads out of diagnostic logs; enforce provider and navigation trust boundaries; release MCP grants after warm CLI turns; preserve sender/account identity across durable retries and scheduled delivery; safer recovery and updates (plugin executables and environment references survive updates; avoid update self-fencing and interrupted-update hangs; repair macOS service recovery when Trash access is denied); native client recovery on iOS/Android and after transient Apple model / computer-use init failures. Release notes count 115 in-range PRs since v2026.11.1. npm package openclaw@2026.11.2 is listed on the tag. Homepage badges showed macOS and Linux on v2026.11.2 while Windows still read v2026.11.1. Soft: docs.openclaw.ai/releases still listed v2026.11.1 as Latest and the dedicated 2026.11.2 docs URL 404’d at close; plugin ClawHub publish was deferred (release notes say that slice remains incomplete); Android APK skipped this train (apps/android/version.json still 2026.8.2). Official @openclaw X account had no original post about the tag in-window.
Standing OpenClaw lane — first new stable tag after v2026.11.1, with named privacy/MCP-grant and atomic-update/recovery work the desk watches every overnight.
More ▾ Less ▴
OpenClaw published stable v2026.11.2 on GitHub at 2026-11-08T19:31:04Z (Mon 2026-11-09 03:31 HKT) — after Sun LIVE — with draft:false, prerelease:false, and release name “openclaw 2026.11.2”. Soft title: platforms / agent-runtime privacy + update-recovery, not a new model and not a re-card of Fri Multiplayer / v2026.11.1. Release highlights center on privacy and trust boundaries: configuration secrets, conversation content, tool errors, and channel payloads stay out of diagnostic logs; provider and navigation trust enforcement; MCP grants released after warm CLI turns; sender/account identity preserved across durable retries and scheduled delivery. Safer recovery and updates: plugin executables and environment references survive updates; avoid update self-fencing and interrupted-update hangs; macOS Trash-denied service recovery; native client recovery on iOS/Android and after transient Apple model / computer-use init failures. Notes count 115 in-range PRs since v2026.11.1; npm lists openclaw@2026.11.2. Stamp: GitHub published Mon 03:31 HKT. Soft gaps at close: docs.openclaw.ai/releases still listed v2026.11.1 Latest and /releases/2026.11.2 404’d; Windows homepage badge still 11.1 (macOS/Linux 11.2); ClawHub plugin publish deferred (full release remains incomplete); Android APK skipped; @openclaw had no original in-window X post.
- Docs “Latest” catch-up to 11.2 and /releases/2026.11.2 resolution
- Windows homepage badge parity with macOS/Linux
- ClawHub plugin publish completion
- Whether v2026.11.5-beta.1 (still prerelease) becomes the next feature-stable
Vendor-confirmed via GitHub release + npm tag assets; Wire did not independently reproduce beyond the public tag. Docs/Windows/ClawHub/Android gaps mean the full release train remains incomplete at close. Not a Fri Multiplayer / v2026.11.1 re-card.