Should you update OpenClaw v2026.11.6? — Update with care
Verdict: Update with care (medium confidence), assessed 2026-11-22.
Evidence: 2 credible blocking issues confirmed for this version, none widespread.
Best version to run today: v2026.11.3 — 12 days in the field, 19 credible known issues, none widespread; last verdict Update with care. If you are on a newer version that works for you, stay put. The latest, v2026.11.6, came out 3 days ago — too new to call settled.
Update with care: macOS users hit a credential-recovery loop, a broken memory plugin, and stuck updates; other platforms face a milder tail
Why this verdict
v2026.11.6 (released 2026-11-19, 406 commits from 386 pull requests) has a cluster of real problems, but they are concentrated rather than widespread. The two credible blockers are both macOS-centric. #203343 (critical, regression): OpenClaw.app 2026.11.6 loops on 'client credentials need recovery' at every launch and instructs the user to run openclaw doctor --fix with a 'matching CLI' that the app never installs — the Mac node stays disconnected. This is a credential-recovery failure, not an update/activation failure, but it is fully blocking for affected desktop users. #202925 (critical): an update from 2026.11.3 toward 2026.11.5 fails activation with update-executor-settlement-failed and state-migrated-no-rollback, and 'openclaw update repair' then permanently refuses with 'Another update executor owns this installation' even though no lease owner exists — a stranded install with no documented recovery path.
Known issues (60+)
- #203343 (critical) [Bug]: macOS app loops on "client credentials need recovery"; asks for a "matching CLI" that can't be installed (app 2026.11.6, app-owned runtime 2026.10.7)
- #202213 (high) [Bug]: 2026.11.6 refuses to read compressed session archives; please ship #192743 and #193548 in a stable release
- #203211 (high) [Bug]: @openclaw/memory-lancedb 2026.11.5 and 2026.11.6 ship only the linux-x64-gnu LanceDB binding; Doctor refuses on macOS arm64
- #202925 (critical) [Bug]:macOS 2026.11.5: update repair refuses executor ownership although shared lease is absent
- #202518 (high) [Bug]: claude-cli run never closes after sessions_spawn + sessions_yield in long sessions; later turns reuse the dead live session
- #202441 (high) Third-party WS channel needs a public way to detach transport authority from post-ACK turn work
- #203167 (high) Codex cooldown persists after a successful GPT-6 Luna request
- #202672 (high) [Bug]: anthropic-messages route: MiniMax-M3.1-Flash intermittently rejected at terminal tool-argument validation (0 on MiniMax-M3)
ClawStat.us gives an independent, evidence-based answer to whether you should update OpenClaw — for every release. Is the latest OpenClaw update safe, or should you wait for the next one? Each verdict is built from post-release bug reports and a two-model review, refreshed every few hours.
Machine-readable: JSON API · llms.txt · full markdown
Independent, unofficial project — not affiliated with or endorsed by OpenClaw or its maintainers. Verdicts are generated automatically and may be wrong; confirm against the linked issues before updating. Data is drawn from the public github.com/openclaw/openclaw issue tracker and releases via the GitHub API.