Should you update OpenClaw v2026.8.2? — Update with care

Verdict: Update with care (medium confidence), assessed 2026-09-04.

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

Best version to run today: v2026.7.1-2 — 31 days in the field, 26 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.8.2, came out 3 days ago — too new to call settled.

v2026.8.2 brings real improvements, but five confirmed blockers — including gateway OOM and a Linux desktop crash — mean update with caution.

Why this verdict

v2026.8.2 ships genuinely valuable work: safer upgrade machinery that preserves newer configuration and recovers a stopped Gateway after a failed update, a security fix in image decoding (Sharp 0.35.4 with libheif 1.23.2), a new Linux desktop app, a dockable Home agent view, and background sessions. But the release carries five credible, confirmed blockers that remain open: #136148 (critical — the Linux desktop AppImage crashes at EGL init or SIGABRTs the WebKit renderer, leaving a permanently blank window), #136452 (critical — compaction.maxActiveTranscriptBytes is silently unenforced for heartbeat-driven sessions, so the transcript grows without bound until the gateway dies with V8 OOM), #136290 (critical — restart recovery can resume stale mutating work hours later and overwrite operator remediation), #136262 (high — openai-completions streams can replay the full accumulated text as a bare text_delta, doubling message content), and #137750 (high — memory-only search can stall the Gateway despite a clean index). None of these has a fix in the shipped stable.

Known issues (60+)

• #136148 (critical) [Bug]: Linux desktop app (2026.8.2 AppImage) — WebKitWebProcess crashes with SIGABRT, leaves blank window
• #136452 (critical) compaction.maxActiveTranscriptBytes is silently unenforced for heartbeat-driven sessions (unbounded transcript growth -> V8 OOM)
• #136183 (high) [Bug]: Command executor hangs when spawning ssh — SIGTERM while waiting for server banner (regression in 2026.8.1, persists in 2026.8.2)
• #137207 (high) [Regression]: visible sessions_spawn child shows Off and the wrong runtime after #78176
• #137337 (high) [Bug]: tools.exec.mode=auto — auto-reviewer is never invoked after approvals migration; every non-allowlisted command falls back to human approval (2026.8.1 and 2026.8.2)
• #137690 (high) [Bug]: sessions_spawn fails with "unknown parent session" for Telegram-originated sessions on 2026.8.2
• #137697 (high) [Bug]: Medium running sessions lead to compaction issues
• #136290 (critical) [Bug]: Main-session restart recovery resumes stale mutating work hours later

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.