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

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

Evidence: 1 widespread breaker(s) (#144911) confirmed for this version.

Best version to run today: v2026.9.1 — 14 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 6 days ago — too new to call settled.

Hold off on 2026.9.4: a slow MCP server can crash the whole gateway, and upgrades from recent versions hit confirmed regressions at multiple stages.

Why this verdict

This release carries a confirmed gateway-killer: #144911 documents that a stdio MCP server failing to initialize within 30 seconds triggers an unhandled rejection ('service child cleanup identity lost') that takes down the entire Gateway process, dropping every channel and session at once. It is the tracker's diamond-lobster rated report with a 29-comment thread and a source-level reproduction, and the Evidence gate marks it as the release's widespread breaker. The same crash path also breaks candidate-Doctor during updates (#146887), and a related event-loop starvation report from a 632-agent fleet (#149538) shows the gateway reaching 'ready' but never serving — critical-severity, P0, open with no fix staged. Because no pre-release exists ahead of 2026.9.4, none of these are patched anywhere a user can install.

Known issues (60+)

• #150707 (critical) [Bug]: Setup wizard dropdown menu keeps looping and cannot proceed in macOS desktop app
• #144911 (critical) [Bug]: MCP server init timeout crashes the Gateway — unhandled rejection "service child cleanup identity lost" in child cleanup path
• #149538 (critical) main (1611ca6d): Gateway reaches ready but never serves; every /health probe times out while the event loop is starved (632-agent fleet)
• #150201 (critical) Windows: update candidate snapshot fails on 2026.9.3; Gateway SQLite check times out
• #145252 (critical) [Tracking] 2026.9.3 / 2026.9.4 update, upgrade and recovery reliability
• #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)
• #144742 (critical) 2026.9.4 ships without #144208: a retained version-1 handoff lease row fails every config write (release blocker)
• #146887 (critical) update 2026.9.3->2026.9.4 fails across four stages: stdio MCP timeout crashes candidate doctor (unhandled rejection), lint hard-gate, then managed-service-handoff-restore-failed

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.