ClawStat.us

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

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

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

Best version to run today: v2026.9.1 — 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.3, came out 2 days ago — too new to call settled.

Hold this update: several upgrade and migration paths break on 2026.9.3 with no fix shipped yet — wait for the next stable or back up first

Why this verdict

v2026.9.3 is a feature-rich release (Safer updates rehearsal, prompt-cache performance, agent-owned Skill Workshop, conversation sharing, meeting library), but it carries a concentrated cluster of upgrade-path failures that directly contradicts the release's own 'Safer updates' theme. #142585 (critical, human-corroborated with a detailed source-level repro and 11 comments) shows the Doctor refusing a valid 2026.7.1-2 → 2026.9.3 legacy workspace/attestation migration with no working repair via 'doctor --fix'; #142586 hits the same journey from another angle, blocking on orphan task_delivery_state foreign keys with no supported recovery path. The update machinery itself misfires on this version: #142394 records an EPIPE shutdown crash with no auto-restart during update.run, #142770 shows a failed 9.2→9.3 update rolling back the runtime while Workshop state has already been forward-migrated (leaving even the rolled-back 9.2 failing Doctor), #142715 leaves the systemd Gateway stopped after a managed pnpm update, and #144132 (critical) shows fresh-profile updates initializing an incompatible database before the target package is even activated. None of these has a fix in any shipped artifact, and there is no pre-release staging relief.

Known issues (60+)

  • #142585 (critical) [Regression]: 2026.9.3 Doctor refuses valid legacy workspace setup and attestation import when canonical rows are absent
  • #142940 (critical) [Bug]: openclaw gateway install` fails with `SERVICE_DEFINITION_UNKNOWN` on systemd 239 (busctl `--json=short` unsupported)
  • #143707 (critical) [Bug]: Claude CLI returns billing error when ample usage room exists
  • #142476 (critical) 2026.9.3: cron session reaper opens every agent database with a synchronous PRAGMA integrity_check, blocking the event loop 14-76s every few minutes on a 632-agent gateway
  • #142394 (critical) [Bug] update.run to v2026.9.3 → EPIPE during shutdown, no auto-restart (managed-service-handoff-restore-failed)
  • #142770 (critical) 2026.9.3: failed update can leave forward-migrated Workshop state on 9.2 rollback; WebChat ACP binding also lacks conversationId
  • #143524 (critical) [Bug]: Agent SQLite WAL grows to 1.4–2.8 GB in days despite wal_autocheckpoint=1000; blocks gateway startup (Windows, 2026.9.2/9.3)
  • #144094 (critical) Gateway crash-loops under launchd on macOS: boots to "ready", then self-terminates within ~1s via [admission] closed: restart drain

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.