OpenClaw Ships v2026.7.2-beta.7: Telegram Reliability, Buzz Markdown Preservation, and Session Tail Fixes

OpenClaw v2026.7.2-beta.7 dropped this morning — 11 commits ahead of yesterday’s beta.6, and almost certainly the last hop before a stable v2026.7.2 release. The headline is Telegram reliability: two of the eleven commits target the channel where users have been quietly suffering the worst.

What Actually Landed in beta.7

The new release ships these user-facing changes on top of yesterday’s beta.6:

  • Buzz messaging: Markdown and structured content preserved end-to-end, plus room- and thread-scoped typing indicators with reconnect-safe lifecycle handling. Buzz has been the roughest of the new channel surfaces, so seeing this in a beta. release — not a “we’ll fix it later” roadmap item — is encouraging.
  • Telegram queue argument validation before any fallback path (#116726). If you’ve ever seen a Telegram delivery fail with a confusing model-failure error that was actually a queue-arg bug, this is your fix.
  • Telegram ingress outcomes preserved across native settings validation (#116773).
  • Sessions: keep restart prompts on the active transcript tail (#117260) — a small but annoying bug where post-restart prompts would land on the wrong pane.
  • Sessions: preserve concurrent ingress result type so two simultaneous ingresses don’t trample each other.
  • QA channel: account evidence isolated and deleted messages excluded (#116744), tightening the test fixtures.
  • CI: PTY tests stay observable and now wait for completed turns (#117405) — a quality-of-life fix for the maintainers more than users, but it should mean fewer flaky-test-induced regressions.

Why This Matters

Honestly? Beta cadence is fast right now. We went beta.3 → beta.5 → beta.6 → beta.7 in roughly two weeks, with each iteration clearly responding to specific issues rather than just bumping version numbers. The Telegram fixes in particular look like direct user feedback making it into the next day’s release.

What I’m watching for: when does beta.7 (or beta.8) graduate to stable v2026.7.2? The state-safety and session-rewind work in the 2026.7.2 series is genuinely significant — if you’re on the stable channel, waiting for the tagged release rather than running betas is the right call, but it’s close.

Install

npm install -g [email protected]

Or pin your beta channel:

openclaw update --channel beta

Source: GitHub Releases – openclaw/openclaw (v2026.7.2-beta.7), published 2026-08-02 08:11 UTC. Diff vs beta.6: GitHub compare.

← Back to News