Should you update OpenClaw v2026.9.6? — Skip this version
Verdict: Skip this version (medium confidence), assessed 2026-09-24.
Evidence: 4 credible blocking issues confirmed for this version, none widespread.
Best version to run today: v2026.9.1 — 21 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.6, came out yesterday — too new to call settled.
Fresh release. OpenClaw v2026.9.6 was published in the last few days — an early read. So far 57 of the issues below name this exact release; the rest are carried over from earlier versions. Bug reports keep arriving in the days after a release, so the issue list usually grows rather than shrinks — the case for waiting only gets firmer over the next few re-assessments. Back up before you update.
Hold off: the macOS app can stop launching after this update, and several npm upgrade paths hang or roll back — a 2026.9.7 fix is coming.
Why this verdict
v2026.9.6's most serious problem is the project's own headline: the changelog warns 'do not update to 2026.9.6 yet' for the macOS app, because the in-app update (#156861) leaves the app crashing on every launch with a Swift concurrency abort, on both a MacBook and a Mac Studio. The report itself is filed as a regression ('worked before, now fails'), the build has been pulled from the Sparkle feed, and a 2026.9.7 hotfix is in progress — but no fixed release or pre-release exists yet, so a macOS app user who updates today can end up with a bricked install until they manually reinstall 2026.9.5. The npm/Gateway package is explicitly stated to be unaffected by that specific crash, but its own update path is shaky: #157011 reports a managed 2026.9.5→2026.9.6 update that 'always rolls back' with a RangeError in update-history reconciliation (reproduced by the reporter), #156986 reproduces a hang in the update-candidate-state phase twice, and #156880 (linux/arm64) and #156992 (darwin/arm64) are update failures in the managed-service-preflight and finalize-plugins phases (each carrying a confirmation note, though the wording is boilerplate in both). Rollbacks are reported as safe, but several users simply cannot get onto this version.
Known issues (60+)
- #156392 (critical) [Bug] Mac Mini M5 Pro macOS: Gateway becomes unresponsive at 100% CPU; recurring heartbeat disabled
- #156424 (critical) [Bug]: Shared-state audit_events index corruption paralyses gateway while process/port stay live (2 incidents, 2026.9.4)
- #156861 (high) fix(macos): update to 2026.9.6 leaves OpenClaw completely unlaunchable on both Macs
- #156985 (high) Kubernetes: /tmp emptyDir lacks sticky protection required by fs-safe, disabling session observer
- #156975 (high) [Bug]: Superseded model-runtime publication triggers provider fallback and misleading quota error on OAuth routes
- #156976 (high) [Bug]: `status --deep` misses stale Homebrew Node path held by running macOS LaunchAgent gateway after brew upgrade
- #156999 (high) Usage: identifiable legacy cron sessions appear as Unattributed in Started by breakdown
- #156880 (high) Update failure: managed-service-preflight (2026.9.4)
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.