Should you update OpenClaw v2026.11.5? — Update with care
Verdict: Update with care (medium confidence), assessed 2026-11-19.
Evidence: No credible blocking issue is confirmed for this version.
Best version to run today: v2026.11.3 — 9 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.5, came out 2 days ago — too new to call settled.
Update with care: most installs run fine, but several reproducible upgrade failures can leave the Gateway stopped — back up state first.
Why this verdict
v2026.11.5 is a feature-rich stable release: restart-safe conversations (#196923, #196540), update rollback on failed Doctor/Gateway startup (#197851), Telegram widgets (#196991), faster memory-index recovery (#196378), and more reliable model fallback (#198427). The deterministic evidence gate comes back ✅, and that baseline matters: across roughly 3 million weekly npm downloads, none of the 60 tracked issues has drawn a single 👍, and no megathread exists. Most users on common configurations are evidently running this release without hitting a widespread breaker.
Known issues (60+)
- #201609 (high) [Bug]: 2026.11.5 Linux: spawn broker dies silently after ~1-2 days and is never respawned; all exec/MCP/cli-backend spawns fail until Gateway restart (regression of #173222?)
- #201634 (high) config validate fails with EACCES ("filesystem did not enforce the private directory DACL") on Windows 10 when a state DB exists
- #201234 (high) [Bug]: Regression in 2026.10+/11.x: `openclaw agent` called from an agent's exec tool is blocked ("would lose inter-session attribution"); sessions_spawn children get no tools under claude-cli runtime
- #201085 (high) [Bug]: failed auto-update leaves Gateway stopped — managed handoff runtime cannot read migrated state (schema 36 vs 22) and recovery probe throws captureExchange is not a function
- #201058 (high) [Bug]: cold Gateway startup on PostgreSQL fails during secrets plugin metadata preparation
- #201124 (high) [Bug]: /stop during preflight compaction silently drops the user message that started the turn (not in transcript, not in interrupted inputs)
- #201468 (high) fix(macos): launch alert gives generic credential recovery steps when the bundled CLI refuses a schema migration for an older Gateway service
- #201561 (high) Windows npm upgrade to 2026.11.5: doctor --fix leaves Gateway stopped; abandoned update still targets 2026.11.3
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.