Should you update OpenClaw v2026.9.9? — Update with care
Verdict: Update with care (medium confidence), assessed 2026-10-10.
Evidence: 4 credible blocking issues confirmed for this version, none widespread.
Best version to run today: v2026.9.8 — 7 days in the field, 11 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.9.9, came out 2 days ago — too new to call settled.
Update with care: confirmed gateway-startup, onboarding, and updater regressions hit Windows, macOS launchd, and new Zen setups, but none is widespread yet
Why this verdict
v2026.9.9 carries four credible blocking issues confirmed against this version, and none shows widespread community traction, which lands the release at a ⚠️ "update with care" verdict. #167636 (regression, names 2026.9.9 exactly) makes onboarding hardcode opencode/claude-opus-5 as the default model even when the user's Zen subscription doesn't include it — every inference then fails until manual config repair, a genuinely bad first-run experience for new subscribers. #168251 (regression) breaks the desktop App Update button with a managed-service-preflight error whenever the Gateway runs as a macOS launchd service with custom npm plugins, compounding the upgrade path for exactly that setup. The Windows startup-hang picture rests primarily on #167406 (Windows MSIX: Codex-enabled Gateway starves the main thread with readiness timeouts) and #167652 (Gateway hangs after a 2026.7.1→2026.9.9 upgrade despite Doctor reporting a verified restart); #167466 corroborates the same symptom cluster but is explicitly reported on 2026.9.8 (a series mention, not an exact 2026.9.9 name), so it is weaker this-version evidence. Windows users upgrading from older versions remain the group most likely to regret updating immediately.
Known issues (60+)
- #167636 (critical) [Bug]: Onboarding forces `opencode/claude-opus-5` as default model even when the Zen subscription doesn't include it
- #168251 (critical) [Bug] App Update button fails with managed-service-preflight when Gateway runs as launchd service with custom npm plugins
- #167406 (critical) [Bug]: Windows MSIX 2026.9.900.0: Codex-enabled Gateway startup starves main thread
- #167466 (critical) [Bug]: Gateway startup hangs for 15+ minutes with sustained single-core CPU and filesystem activity
- #168366 (high) [Bug]: Telegram richMessages: a table followed by a blockquote is nested inside it, followed by a list it is dropped (2026.9.2–2026.9.9 regression vs 2026.7.1)
- #167694 (high) [v2026.9.9] Agent autonomy regression: auto-review blocks routine shared-infrastructure work that 9.5 agents could do
- #167385 (high) [Bug]: hand-deleted sessions-delete archive (.jsonl.deleted.*.zst) permanently blocks plugin session repair, codex data upgrade and update verification
- #167652 (high) [Bug]: Windows Gateway hangs after 2026.9.9 upgrade despite Doctor reporting verified restart
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.