OpenClaw v2026.6.8-beta.1 landed on June 13th with a broad reliability pass across channel delivery, Gateway recovery, provider routing, usage hooks, UI state, memory indexing, and release validation. It follows v2026.6.7-beta.1, which shipped earlier the same day, so operators tracking the beta channel have two fresh release trains to review before the next stable cut.
The official release notes describe the theme clearly: Telegram and WhatsApp are getting richer, agents recover more cleanly, and model/provider handling is being tightened before these changes graduate to stable.
Channels Get the Biggest Lift
The headline change is channel delivery. Telegram now supports richer structured output, including tables, lists, expandable blockquotes, and safer media boundaries. The same release also preserves prompt handoff for CLI backends, which matters when Telegram is used as a real operating surface rather than a thin notification layer.
WhatsApp gets a smaller but important fix: ACP bindings now respect configured behavior. That is the kind of change that usually only matters when something is broken in production, but for multi-channel OpenClaw installs it keeps the channel abstraction honest.
Related fixes also touch Slack outbound message_sent hooks, same-channel generated media completions, Telegram thread-create remapping, and chunking around surrogate pairs and unbounded chunk limits.
Runtime Recovery Keeps Improving
Several fixes target the failure paths that make autonomous systems feel brittle:
- Active main sessions are marked before restart shutdown aborts.
- Yielded subagent runs can pause correctly when the terminal also signals abort.
- Cron media completions are preserved after yielding.
- Main-session heartbeat events are deduplicated.
- Unknown OpenAI agent selectors are rejected instead of drifting into ambiguous behavior.
- HTTP session and model override surfaces now require admin privileges.
The release notes also call out account-scoped DM send policy preservation, generated media completions, session identity prompts, and restart shutdown behavior. Taken together, this beta is less about one dramatic feature and more about closing the gaps where long-running agents lose track of who they are replying to, what they already delivered, or which state was terminal.
Providers and Models Expand Carefully
OpenClaw adds GLM-5.2 support and Claude Haiku 4.5 catalog rows in this beta, while also normalizing provider-qualified model IDs across OpenRouter and Google Vertex paths. That provider-prefix cleanup is easy to underestimate: model IDs flow through CLI backends, managed providers, replay logic, UI selectors, and tool-streaming decisions.
Other provider fixes include managed SecretRef auth, bounded model browsing, nested embedding error surfacing, and storeless OpenAI Responses replay gating. Claude 4.5 Copilot tool-streaming behavior also gets a safety fix.
Usage Footers Become Native
Usage display gets a native full-footer renderer with a default template, fixed-decimal formatting, credential-aware limits, and warnings for broken templates. For operators who use /usage or reply payload hooks in production chat surfaces, this should make usage output less custom, less fragile, and easier to trust.
That is especially useful for shared assistants where cost and quota visibility need to appear in the same channel where work happens.
UI, Memory, and State Fixes
The UI side gets steadier too. Workspace files can start collapsed, WebChat backscroll survives streaming, the sidebar session picker remains interactive above the desktop workbench, and iOS gateways reconnect after stale foreground states.
Memory and state fixes include splitting oversized OpenAI embedding batches before 431 errors, keeping QMD memory search available in transient mode, avoiding SQLite WAL on NFS state volumes, preserving stuck-session warning backoff, and keeping Infinity chunk limits genuinely unbounded.
Should You Upgrade?
If you run beta builds and rely on Telegram, WhatsApp, generated media, provider-prefix routing, or cron/heartbeat delivery, this is a high-value beta. Stable-channel operators can wait, but the release notes are worth reading now because the changes point toward the next stable focus: richer channel output, safer recovery, and more predictable provider selection.
Read the full release notes on GitHub: OpenClaw v2026.6.8-beta.1.