Should you update OpenClaw v2026.10.4? — Update with care
Verdict: Update with care (medium confidence), assessed 2026-10-18.
Evidence: 2 credible blocking issues confirmed for this version, none widespread.
Best version to run today: v2026.10.1 — 8 days in the field, 2 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.10.4, came out 2 days ago — too new to call settled.
Update with care: useful stability fixes, but updater restarts, Windows startup/doctor hangs, and Talk session bugs remain open
Why this verdict
v2026.10.4 is a stability patch over 2026.10.3 with real improvements — the gateway now survives sleep and clock jumps without restarting itself (#170790), shutdown hangs on stalled transcript workers are fixed (#170493, #170555), and an owner-impersonation path in Tlon group DMs is closed (#165801). For most users on a healthy install, updating is reasonable, but two credible blockers keep this at 'update with care'. First, #174373 (human-confirmed, 🦞-rated) shows the 2026.10.4 package updater can restart a running Gateway despite --no-restart while its messaging claims it won't — its underlying main-branch fix (#171311) is absent from both the stable cut and the v2026.10.10-beta.1 pre-release, so relief is not yet shipped. Second, #175027 (🦞-rated) reports Android realtime Talk binding to an archived backing session and rejecting GPT-Live agent consults — though the reproduction runs Android app build 2026.10.30 against Gateway 2026.10.3, so part of its blast radius may belong to the next release's evidence.
Known issues (60+)
- #175027 (high) [Bug]: Android realtime Talk reuses archived backing session and rejects GPT-Live agent consults
- #175062 (high) [Bug]: Background exec completion continuation loses conversations_send available to scheduled main run
- #175360 (high) [Bug] openclaw delegator fails with Inference setup probe cleanup did not finish safely
- #175794 (high) [Bug]: Realtime Talk (gateway-relay) WebSocket bypasses managed proxy (proxy.proxyUrl) – "Realtime provider error" on egress-restricted hosts
- #176111 (high) [Bug]: Windows Gateway startup fails with DataCloneError - schema-inspection worker IPC sends the win32 env Proxy through advanced serialization (b1e6a6b, 2026.10.4)
- #174373 (high) [Tracking] 2026.10.4 package updates: deliver no-restart reporting fix and qualify macOS handoff
- #174443 (high) Update failure: package-swap (2026.9.8)
- #174842 (high) [Bug] doctor --fix hangs in unbounded SQLite read-only-snapshot loop with Gateway running (2026.10.4); SIGTERM ignored, SIGKILL required after 26+ min
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.