Should you update OpenClaw v2026.10.8? — Too new to call
Verdict: Update with care (medium confidence), assessed 2026-10-28.
Evidence: 1 credible blocking issue confirmed for this version, none widespread.
Best version to run today: v2026.10.5 — 10 days in the field, no credible known issue; last verdict Safe to update. If you are on a newer version that works for you, stay put. The latest, v2026.10.8, came out yesterday — too new to call settled.
Fresh release. OpenClaw v2026.10.8 was published in the last few days — an early read. So far 58 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.
Update with care: a quiet release overall, but Windows onboarding can fail at activation and several channel and model-policy bugs remain open
Why this verdict
v2026.10.8 is a comparatively calm release — 60 tracked issues versus 78–85 for each of the four prior releases, and near-zero community engagement (7 thumbs-up total, max 4 on any single issue, against ~2.7M weekly npm downloads) — but the evidence gate names one credible blocker, #185819, which moves this assessment from the prior ✅ to ⚠️. That issue pins the release series: on native Windows 10, interactive quick-start Codex onboarding completes device authorization and then fails activation with an 'inactive harness runtime artifact' error, bouncing the user back to provider selection (8 comments, the most-discussed report in this set). If you are setting up fresh on Windows, that is a real risk; existing installs are unaffected by it.
Known issues (60+)
- #186434 (high) [Bug]: Claude 5.x via third-party Anthropic-compatible proxy answers the runtime-context carrier instead of the user message (consecutive user turns on non-direct `anthropic-messages` routes)
- #186281 (high) Plugin scheduled command turns ignore the requester's tool policy and apply the guest `toolsBySender["*"]` entry
- #186333 (high) [Bug]: Microsoft Teams stops applying startup-resolved allowlists after an unrelated config reload
- #186414 (high) [Bug] Windows WhatsApp owner DM repeatedly fails keyed-user transcript assertion after session reset and 2026.10.8 upgrade
- #186478 (high) pdf tool: bogus model candidate when provider model ids contain slashes (splits fully-prefixed ref on first "/" → 404 for model=)
- #186043 (high) 2026.10.7 regression: heartbeat SessionBindingError (discord delivery resolves to nonexistent "default" account) + event-loop starvation via fetchWithSsrFGuard against dead provider host
- #185819 (high) [Bug]: Windows quick-start Codex onboarding completes device authorization, then fails activation with inactive harness runtime artifact (2026.10.7)
- #185817 (high) Model setup wizard hangs at 'Testing your AI connection...' after its config write lands; the model change stays live after restart
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.