Should you update OpenClaw v2026.9.4? — Skip this version

Verdict: Skip this version (medium confidence), assessed 2026-09-12.

Evidence: 13 credible blocking issues confirmed for this version, none widespread.

Best version to run today: v2026.9.1 — 9 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.4, came out yesterday — too new to call settled.

Hold off: a missing handoff-lease fix breaks config writes and self-updates on hosts with older state, and no pre-release carries the repair yet

Why this verdict

v2026.9.4 shipped without fix #144208 (main commit 00edac8, merged after the release branch was cut), and per the maintainer-reviewed, P0 report #144742 that omission means any host carrying a legacy version-1 handoff lease row fails every config write — 'openclaw config set', Doctor repairs, plugin convergence, and even already-current updates — until a temp file is manually deleted. The same root cause chains into the self-update path: #145192 documents three identical, deterministic failures of a managed 2026.9.2 → 2026.9.4 update on macOS at the candidate-Doctor step, with a rollback that lands on 9.4-migrated state. There is still no pre-release ahead of this stable, so the fix that maintainers have already verified on main exists nowhere a user can install.

Known issues (60+)

• #144788 (critical) [Bug]: runDetachedWebhookWork no longer acquires an AsyncWorkScope in 2026.9.4, breaking async post-agent_end embedded-agent work
• #144742 (critical) 2026.9.4 ships without #144208: a retained version-1 handoff lease row fails every config write (release blocker)
• #145192 (critical) 2026.9.2 → 2026.9.4 managed update fails at candidate-Doctor on a live v1 handoff lease, then rolls back onto 9.4-migrated state (#144742 upgrade path)
• #144639 (critical) Update failure: post-update-plugins (2026.9.4)
• #144825 (critical) Update failure: repairing (2026.9.3)
• #144706 (critical) Update failure: managed-service-handoff-unsafe-recovery (2026.9.4)
• #144718 (critical) Update failure: node-runtime-preflight (2026.9.4)
• #144735 (critical) Update failure: [redacted-command] (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.