Should you update OpenClaw v2026.9.7? — Too new to call

Verdict: Too new to call — no credible blocker so far, not an all-clear yet (medium confidence), assessed 2026-09-30.

Evidence: No credible blocking issue is confirmed for this version.

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

Fresh release. OpenClaw v2026.9.7 was published today — an early read. So far 16 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 more problems may still surface; treat this as provisional and re-check over the next few re-assessments. Back up before you update.

Safe to update for most setups; a few low-traction npm update-failure reports exist, but rollbacks are verified safe.

Why this verdict

v2026.9.7 is a update-safety-focused release that lands cleanly by the evidence: no credible blocking issue is confirmed for this version, community engagement across all 18 tracked issues totals just 7 👍 (max 4 on any single report) against an install base of ~3.4M weekly npm downloads — a blast radius consistent with normal ambient churn, not a widespread breaker. Notably, this release carries far fewer tracked issues than its predecessors (18 vs 78–95 for 2026.9.3 through 2026.9.6), and its changelog directly hardens the upgrade path: automatic state and agent database backups before migrations with rollback restore (#158163, #158317, #156265) and fixes for managed-update stack-overflow rollbacks, Windows migration stranding, and macOS handoff activation (#157273, #157262, #156972, #157756, #160015).

Known issues (18)

• #161590 (high) Update failure: global-install-failed (2026.9.3)
• #161593 (high) update.run reports success but spawns helper inside gateway process tree, making update impossible
• #38327 (critical) [Bug] "Cannot convert undefined or null to object" in 2026.3.2 with google-vertex/gemini-3.1-pro-preview
• #48920 (critical) [Bug]: Live Docs are ahead of release
• #161506 (high) Session lane task stuck active (activeAhead=1 activeNow=0) starves queued turns; scheduled runs burn their wall clock with zero dispatch
• #161522 (high) [Bug]: Bun WebSocket proxy path imports undeclared proxy-from-env dependency
• #161458 (high) Update failure: global-install-failed (2026.9.3)
• #161468 (high) [Bug]: Auth profile cooldown bookkeeping rebuilds every prepared model runtime and can starve catalog readers indefinitely

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.