ClawStat.us

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

Verdict: Update with care (medium confidence), assessed 2026-10-29.

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

Best version to run today: v2026.10.6 — 7 days in the field, 3 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.9, came out today — too new to call settled.

Fresh release. OpenClaw v2026.10.9 was published today — an early read. So far 30 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: valuable security patches, but two credible core bugs (agent database corruption, Doctor migration stalls) remain unfixed

Why this verdict

v2026.10.9 is a maintenance release with real security value: it patches vulnerable runtime dependencies (fast-uri URI validation, nodemailer 10.1.4 IMAP sender-spoofing protection, MSAL Node 7.1.1 for Teams), applies tools.fs.workspaceOnly to Gateway-built tools, and keeps live credentials out of MCP CLI inspection and logs. For users running exposed gateways or chat-channel integrations, those are meaningful reasons to move to this version rather than stay on 2026.10.8.

Known issues (31)

  • #187309 (critical) Recurring per-agent SQLite WAL/SHM identity mismatch after active-leases close receipts on 2026.10.8
  • #187435 (high) Telegram sendMessage regression — high failure rate after 2026.10.7 update
  • #187383 (high) [Bug]: activation Doctor loses state lease heartbeat during database migrations
  • #187579 (high) [Bug]: Pi500 restart generates 1.5 GB of unnecessary writes and reports ready too early
  • #187588 (high) [Bug]: Telegram: a standalone MEDIA: line for an existing local PDF is never dispatched — text delivered, zero document send, no error logged
  • #187114 (high) [Bug]: claude-cli conversations reset with reason=mcp after ToolSearch deferral (#186776)
  • #187115 (high) [Bug]: one failed Claude CLI launch makes every later turn in that conversation fail with the same error
  • #187242 (high) [Bug]: claude-cli post-turn compaction ignores ownsNativeCompaction after a NO_REPLY/"empty response" turn and fails with "No API key found for provider anthropic"

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.