releaseintermediate
[Release] openclaw/openclaw v2026.7.2-beta.7: openclaw 2026.7.2-beta.7
By github-actions[bot]github
View original on githubOpenClaw v2026.7.2-beta.7 introduces major stability and feature enhancements including state safety with quarantine stores and crash-recoverable snapshots, durable channel delivery across multiple platforms, session rewind/branching capabilities, interactive MCP Apps with dashboards, structured questions and approvals, meeting integration with Teams/Zoom/Google Meet, Wear OS companion app, and guided local inference setup. The release also adds Claude Opus 5 support, native app improvements across macOS/Linux, enhanced memory recall, scheduling with dynamic cadence, Fish Audio speech synthesis, and numerous security hardening fixes.
Key Points
- •Implement state safety through quarantine stores that survive database damage and crash-recoverable SQLite snapshots with rollback-writer recovery
- •Enable durable channel delivery across Telegram, Signal, Slack, QQBot, Twitch, Synology Chat, Tlon, IRC, and Zalo with shared ingress drain and dead-letter recovery
- •Support session rewind and branching with conversation forking from individual messages and branch-safe queued sends across web and native apps
- •Host interactive MCP Apps with ticketed hosting, bound tools/resources, and bounded context updates accessible from channel replies and durable dashboards
- •Deploy structured questions and approvals with option cards across web, channels, macOS, and native apps including push notifications and fair queuing
- •Integrate Teams, Zoom, and Google Meet calls with default-enabled meeting plugins and durable transcript collection
- •Add Wear OS companion with home-screen agent/session/model selection, realtime Talk controls, and audio-reactive playback
- •Provide guided setup with local-provider detection, downloadable models, and in-process RAM-gated llama.cpp/Gemma inference path
- •Support Claude Opus 5, Kimi K3, and GPT Live realtime with Platform API authentication
- •Enhance security with channel allowlist fixes, forged-marker bypass closure, unsafe approval ID rejection, and secret redaction hardening
Found this useful? Add it to a playbook for a step-by-step implementation guide.
Workflow Diagram
Start Process
Step A
Step B
Step C
Complete