OpenClaw v2026.7.2-beta.7: Local inference and setup, delivery notes

v2026.7.2-beta.7 is a channel and session story. The official source describes a channel, client, interface, or browser change, and the important question is what survives the handoff between a Gateway, a conversation, and a reconnect.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Follow the message path

01 / State safety and recovery

Source signal. protect 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.

Test State safety and recovery at the edges of the interface: clean start, reload, reconnect, and a refused or unavailable action. Keep the final screen and error message with the release note.

02 / Durable channel delivery

Source signal. keep accepted messages recoverable across gateway restarts and local crashes through the shared ingress drain and dead-letter recovery, covering Telegram, Signal, Slack, QQBot, Twitch, Synology Chat, Tlon, IRC, and Zalo User. #108656, #107246, #109911.

The operator question around Durable channel delivery is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

03 / Session rewind and branching

Source signal. rewind or fork conversations from individual messages, switch transcript branches across web and native apps, fork upstream Codex sessions, preserve branch-safe queued sends, reject stale-pane writes, and restore prompt images after a fork.

The operator question around Session rewind and branching is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

04 / Interactive MCP Apps and dashboards

Source signal. host ticketed MCP Apps with bound tools, resources, and bounded context updates; open them from channel replies, pin them to durable dashboards, harden their shared sandbox, and let native plugins declare them directly. #109851, #110451, #113218.

The useful evidence for Interactive MCP Apps and dashboards is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

The less visible details

Questions and approvals everywhere

let agents ask structured questions with option cards across web, channels, macOS, and native apps, while approvals gain push notifications, history, fair queuing, headless resolution, Claude tool-request relay, reviewer detail, and clearer formatted prompts. #85954.

Treat Questions and approvals everywhere as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Models and providers

add Claude Opus 5 across catalog and runtime, Kimi K3, and GPT Live realtime support with the supported Platform API authentication path. (#113391, #113392, #113633; #113909, #113354.

The useful evidence for Models and providers is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Local inference and setup

detect local inference providers during onboarding, add in-process llama.cpp GGUF inference and Baseten Model API support, discover models from live provider catalogs, and offer model downloads from web and macOS setup.

Local inference and setup changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising State safety and recovery.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
4. Compare the transcript before and after reconnect, including delivery state and any visible error.
5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Security and authorization. prevent channel allowlists from granting owner access, keep session exports inside the workspace, close a forged-marker/web-search boundary bypass, prevent non-owner ACP session exposure, reject unsafe explicit approval IDs, harden secret redaction and exec/OAuth approvals, validate downloaded install scripts, and prevent insecure secrets-plan writes. Keep the reproduction and the post-fix result together in the acceptance record.

SQLite and data safety. commit session indexes before transcript eviction, preserve state through maintenance races and live-WAL verification, reject invalid backups and schema data loss, make snapshot publication crash-recoverable, retain complete backups after interrupted commits, and evict only the exact corrupted cached database owner so repairs recover without a Gateway restart. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.7.2-beta.7 release notes for the exact change list, then cross-check the official release index and the channel routing guide before acting.