ClawStat.us release health

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

Verdict: Skip this version (high confidence), assessed 2026-06-20.

v2026.6.8 ships critical regressions across Telegram, memory, gateway startup, and cron; pre-release v2026.6.9-beta.1 is brewing with potential fixes

Why this verdict

The v2026.6.8 release introduces multiple critical regressions that break core functionality. Telegram web users encounter 'This message is currently not supported on Telegram Web' (#93794, 8 👍), a regression from v2026.6.5. The gateway crashes on startup with ERR_MODULE_NOT_FOUND (#94570, regression of #72042), preventing any use. Memory search intermittently fails with 'index metadata is missing' (#90361, 3 👍), and isolated cron jobs time out during tool execution (#94033). Additionally, Telegram isolated ingress can saturate the event loop when process.env is large (#94571), and the Telegram richMessages regression still ships despite docs describing opt-in (#94885). These issues are all confirmed against v2026.6.8 and have no shipped fixes. The pre-release v2026.6.9-beta.1 (published 2026-06-19) may carry fixes, but they are not yet in the stable channel. An independent validator reviewed the prior assessment and agreed with the ⏸️ recommendation, flagging one miscategorization: #94131 (Telegram iOS font size regression) should be tagged 'regression' rather than 'post_release' since the issue body explicitly identifies it as introduced by PR #92679 in v2026.6.8 and absent in v2026.6.6 — this has been corrected. The validator's other observation about #91902's version field discrepancy (body says 2026.6.5, yet AFFECTS THIS VERSION is marked) is noted but does not change the categorization or recommendation. Given the severity and breadth of these regressions, upgrading to v2026.6.8 is risky; users should wait for the next stable release that addresses these blocking issues. The prior assessment also placed this version at ⏸️, and the broken-state has not improved — new critical issues like #94570 and #93794 have surfaced, reinforcing the need to skip.

Known issues (60)

  • #93794 (critical) [Bug]: Messages on v2026.6.8 no longer supported on telegram web
  • #90361 (critical) [Bug]:Intermittent memory_search "index metadata is missing" despite valid builtin memory index; likely search/reindex race. Locally hotfixed.
  • #94033 (critical) Bug: Cron isolated agent timeout during long tool execution
  • #94571 (critical) Telegram isolated ingress copies large process.env in queue hot path
  • #94570 (critical) [Bug]: Gateway startup fails after update to 2026.6.8 — ERR_MODULE_NOT_FOUND for server-chat-DVXWYmKw.js (regression of #72042)
  • #91363 (high) Isolated cron consistently fails with "LLM request failed" on model-call-started phase
  • #94131 (high) Telegram iOS font size setting ignored in v2026.6.8 — bot messages render at fixed larger size
  • #93775 (high) [Bug]: Refreshable provider catalogs can skip runtime discovery

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.