Should you update OpenClaw v2026.7.1-2? — Update with precautions
Verdict: Update with precautions (medium confidence), assessed 2026-08-04.
Fresh release. OpenClaw v2026.7.1-2 was published today — an early read. So far 19 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 more problems may still surface; treat this as provisional and re-check over the next few re-assessments. Back up before you update.
A minor fix release with a few concerning but unconfirmed data-loss reports from the beta channel — update with caution; a fix release is in the works.
Why this verdict
OpenClaw v2026.7.1-2 ships a single targeted fix: npm plugin metadata handling so official plugins can install and update correctly. The release introduces no new features or breaking changes, making it a low-risk quality-of-life patch for plugin users. However, two critical data-loss bugs (#119088, #119090) have been reported on the v2026.7.2 beta series — they can permanently delete generated media when `attachments.ttlHours` is set or when the session store is unreadable. While these bugs are not confirmed on the stable release, the underlying code paths may be shared, so users who rely on managed media or the TTL sweep should exercise caution. A Slack preview streaming bug (#119041) is confirmed on this exact stable version, causing message rotation on MiniMax reasoning boundaries, and a deferred maintenance timeout issue (#119117) can leave stale running tasks that resist cleanup. None of these have fixes in the current stable distribution, but the pre‑release v2026.7.2‑beta.7 is actively staging remedies, and the Telegram duplicate‑delivery bug (#119048) already has a merged fix targeting a future stable. Community engagement is extremely low (16 total 👍 across all tracked issues, max 4 on any single issue), indicating no widespread breakage. The STRICT migration crash (#110186) is specific to the v2026.7.2 beta line and does not affect this stable version. Most users can safely update with the precautions above, and relief is near.
Known issues (21)
- #119088 (critical) [Bug]: attachments.ttlHours sweeps media/outgoing, deleting chat-history managed media and lifting the managed-image migration barrier
- #119090 (critical) [Bug]: managed media cleanup fails open on an unreadable session store and permanently deletes a session's generated media
- #119041 (high) [Bug]: Slack partial preview rotates into new messages on MiniMax reasoning boundaries
- #110186 (critical) v2026.7.2 STRICT migration fails on databases with BLOB-stored TEXT values and PRIMARY KEY constraints
- #48920 (critical) [Bug]: Live Docs are ahead of release
- #119018 (high) [Bug]: delegated context-engine compaction gets the sessionId in place of sessionKey — every compaction fails as reason=unknown
- #119079 (high) [Bug]: Talk realtime transcript persistence fails on STRICT session store — cannot store REAL value in INTEGER column session_nodes.updated_at (beta.6 + beta.7)
- #119117 (high) [Bug]: Deferred turn maintenance has no timeout; resulting stale running rows cannot be cleared by any supported command
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.