Should you update OpenClaw v2026.6.8? — Wait for next release
Verdict: Wait for next release (medium confidence), assessed 2026-06-18.
Fresh release. OpenClaw v2026.6.8 was published in the last few days — an early read. So far 41 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 the verdict firms up over the next few re-assessments. Back up before you update.
Wait for next release: v2026.6.8 delivers strong channel and model improvements but is undermined by critical regressions and a broad set of high‑severity post‑release issues; fixes are in progress but not yet confirmed in the beta pre‑release.
Why this verdict
v2026.6.8 introduces substantial upgrades like Telegram rich‑text, native /usage footers, new GLM‑5.2 and Claude Haiku 4.5 entries, and better memory resilience. The previous assessment flagged ⚠️, but the broken‑state has materially worsened since then. Critical regressions now break Telegram Web delivery entirely (#93794), cause intermittent memory‑search “index metadata is missing” failures (#90361), and abort long‑running isolated cron tools because progress notifications are absent (#94033). These alone would justify downgrading to 🔄, but the validator correctly notes that several additional high‑severity, version‑specific issues were omitted from the original analysis. Feishu plugin discovery is broken on Windows (#93908), the Docker sandbox fails with duplicate mount points on reserved paths (#93854), sub‑agent sessions inconsistently lose write and MCP tools (#94158), and Codex native thread churn wastes context (#93750). The memory‑wiki stale‑pages report flags durable references incorrectly (#93485), and the cron list returns incomplete results after SQLite migration (#94155). This wider defect profile confirms that the release carries an unusually high aggregate severity load.
Known issues (47)
- #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
- #91363 (high) Isolated cron consistently fails with "LLM request failed" on model-call-started phase
- #93775 (high) [Bug]: Refreshable provider catalogs can skip runtime discovery
- #94131 (high) Telegram iOS font size setting ignored in v2026.6.8 — bot messages render at fixed larger size
- #93485 (high) memory-wiki: Stale Pages report flags intentionally durable references (concepts, syntheses) as aging
- #93750 (high) [Bug]: Codex native threads churn when subagent announce turns remove message
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.