Should you update OpenClaw v2026.7.1-2? — Update with precautions
Verdict: Update with precautions (medium confidence), assessed 2026-08-29.
v2026.7.1-2 stays at ⚠️: multiple critical-severity data-loss and resource-exhaustion bugs remain unfixed on stable, but near-zero engagement shows contained blast radius, with relief staged in v2026.9.1-beta.1
Why this verdict
v2026.7.1-2 remains a 'update with precautions' release. The tier-1 evidence is a cluster of critical-severity, unfixed data-loss and resource-exhaustion bugs that all name this exact version: #125570 (Skill Workshop updates silently overwrite a live skill's capability description, destroying skill routing — source-repro, 🦞 diamond lobster, impact:data-loss), #126906 (denying the write tool via tools.deny silently disables memory persistence while the agent reports success — source-repro, 🦞, impact:data-loss), #126423 (macOS Voice Mode fails to save voice dialogs — complete conversation loss, reproducible every time), #125344 (memory-core embedding workers and Codex app-servers leak with no idle TTL, silently strangling the gateway cgroup with no OOM kill — measured on production), #130807 (a stale /tmp mount wedges the gateway at 100% CPU in an unkillable synchronous mkdir loop, reproduced identically on 2026.7.1-2), and #127139 (a confirmed regression where Codex progress messages can still silently end a multi-step turn despite the #108487 fix shipped in this release). None of these has a fix PR landed (clawsweeper:no-new-fix-pr across the board), and any fixes will arrive only via a future stable release — the current pre-release v2026.9.1-beta.1 does not lift this verdict because nothing is shipped to the stable channel yet.
Known issues (60+)
- #127139 (critical) [Bug]: Codex progress message(action=send) still ends turn after #108487 when final is omitted and stopReason is toolUse
- #125344 (critical) memory-core local embedding workers and codex app-servers leak with no idle TTL, strangling the gateway cgroup
- #125570 (critical) [Bug]: Skill Workshop update apply overwrites the live skill's description, silently breaking skill routing
- #125333 (critical) totalTokens inflation still reproduces on 2026.8.1-beta.2: #123065 fix only covers `api === "cli"`, and the memory-flush transcript path is an unguarded ratchet
- #126906 (critical) Denying the write tool silently disables memory persistence, and the agent reports success anyway
- #126423 (critical) [Bug]: P0 CRITICAL: Voice Mode deletes conversations & breaks layout
- #119281 (critical) [Bug]: Update fails during doctor checks due to Node.js version requirements (Node v24.12.0)
- #130807 (critical) Gateway wedges at 100% CPU (unkillable without SIGKILL) when /tmp becomes a stale mount: unguarded recursive mkdirSync at logger module load never returns
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.