OpenClaw published v2026.7.2-beta.7 on August 2, bringing another large beta build focused on state safety, durable channel delivery, session branching, MCP Apps, setup, and realtime communication.
The release arrived after the morning aggregation cutoff, which makes it the headline item for tonight's OpenClaw Chronicles run. The npm beta tag also advanced to 2026.7.2-beta.7, matching the GitHub release.
The Big Theme
The release notes frame this beta around reliability across the places where agent systems usually fail: storage, delivery, auth, setup, and long-running sessions.
OpenClaw says the state-safety work protects persisted data with a quarantine store that survives primary database damage, crash-recoverable SQLite snapshots, crash-durable filesystem publication, schema-upgrade data-loss rejection, and rollback-writer snapshot recovery.
That is not a single feature so much as a hardening wave. For operators, the key point is that OpenClaw keeps moving more recovery behavior into explicit owners instead of leaving it as best-effort startup repair.
Delivery, Sessions, and Apps
Durable channel delivery is another major section. The release notes say accepted messages are recoverable across Gateway restarts and local crashes through shared ingress drain and dead-letter recovery. The covered channels include Telegram, Signal, Slack, QQBot, Twitch, Synology Chat, Tlon, IRC, and Zalo User.
The session model also keeps expanding. Beta 7 highlights message-level rewind and fork, transcript branch switching across web and native apps, upstream Codex session forks, branch-safe queued sends, stale-pane write rejection, and prompt-image restoration after a fork.
MCP Apps get a broader role too. OpenClaw now highlights ticketed MCP Apps with bound tools, resources, bounded context updates, channel-reply launch paths, durable dashboard pins, sandbox hardening, and native plugin manifest declarations.
Setup and Realtime Work
The release includes more setup and model-provider changes:
- Claude Opus 5 catalog and runtime support
- Kimi K3 support
- GPT Live realtime support through the supported Platform API authentication path
- local-provider detection during onboarding
- in-process llama.cpp GGUF inference
- Baseten Model API support
- live-provider catalog discovery
- downloadable model flows in web and macOS setup
Meetings and realtime Talk also get a large entry. The release notes mention Teams, Zoom, and Google Meet guests, default-enabled meeting plugins, durable transcript collection, OpenAI and Gemini video, and a clearer requirement for a supported OpenAI Platform API key instead of a rejected Codex OAuth fallback.
Verification
The release verification section links the npm package, registry tarball, integrity value, release SHA, CI evidence, publish workflow, npm preflight, full validation workflow, and plugin publish workflow.
That evidence matters because this beta bundles many operator-facing changes. The changelog spans state recovery, channels, provider behavior, native apps, memory, scheduling, security, and install paths. In a release that broad, validation links are part of the story, not an appendix.
For teams running the beta channel, v2026.7.2-beta.7 looks like a recovery-and-operations release: less about one marquee screen, more about making OpenClaw behave predictably after restarts, upgrades, long sessions, and channel edge cases.