Should you update OpenClaw v2026.6.9? — Skip this version
Verdict: Skip this version (medium confidence), assessed 2026-06-23.
v2026.6.9 delivers richer Telegram and Codex integration but is blocked by critical memory regressions, a new high‑severity model‑pin regression, and a thick swarm of post‑release bugs; skip and wait for v2026.6.10‑beta.2 fixes.
Why this verdict
v2026.6.9 ships valuable improvements – richer Telegram delivery, more dependable agent recovery, a stronger Codex integration, and standalone official provider plugins – but the release is weighed down by multiple critical and high‑severity regressions and a dense clutch of post‑release issues. The most severe blockers remain #95495 (silent memory‑store relocation that forces a full 1499‑file re‑embed with zero upgrade‑time warning) and #90361 (intermittent memory_search “index metadata is missing” concurrency race). These two critical memory regressions alone make the release unfit for production, especially for users with large memory corpora.
Known issues (43)
- #90361 (critical) [Bug]:Intermittent memory_search "index metadata is missing" despite valid builtin memory index; likely search/reindex race. Locally hotfixed.
- #95495 (critical) [Bug]: 2026.6.9 silently relocates memory store with no migration, forcing a full re-embed (1499 files) with zero upgrade-time warning
- #95515 (critical) Upgrade 2026.6.8→2026.6.9 corrupts email channel config with spurious groupAllowFrom field
- #91363 (high) Isolated cron consistently fails with "LLM request failed" on model-call-started phase
- #95623 (high) tool_use.id sanitizer (#61254) misses OpenAI-responses composite id on cross-provider failover replay → Anthropic 400 bricks session
- #94518 (high) DeepSeek cache hit rate <10% after 6.x upgrade - boundary-aware caching breaks prefix matching
- #95489 (high) [Bug]: claude-cli out-of-credits error bypasses model fallback chain — error text delivered as final response
- #95535 (high) sessions_yield does not resume on isolated cron run completion; docs/tool description should clarify
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.