Tutorial

OpenClaw v2026.7.2-beta.5: Questions and approvals everywhere, for maintainers

July 28, 20266 min readUpdated September 11, 2026By OpenClawBlog Team

For maintainers reading v2026.7.2-beta.5, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.

This candidate is still pre-release. Treat provider, channel, and migration behavior as unconfirmed until your own bounded test passes. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Channel
Pre-Release

Primary signals
State safety and recovery; Durable channel delivery; Session rewind and branching

Publication date
2026-07-28

Compatibility for maintainers

State safety and recovery

Evidence from the release. 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.

Operator reading. 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.

Durable channel delivery

Evidence from the release. 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.

Operator reading. For Durable channel delivery, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

Session rewind and branching

Evidence from the release. 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.

Operator reading. For Session rewind and branching, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

Interactive MCP Apps and dashboards

Evidence from the release. 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.

Operator reading. 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.

API, package, and test clues

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 through Codex OAuth. (#113391, #113392, #113633; #113909, #113354.

Read Models and providers as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

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.

A catalog label for Local inference and setup is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

Run the smallest useful rehearsal

Write down the baseline for State safety and recovery, including the installed version, host, provider, and workspace.
Confirm what can be restored, then take a verified backup before applying the candidate package.
Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw security audit

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Fix details to carry forward

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. This is the edge case to include in a regression check, especially when the release is pre-release.

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, and retain complete backups after interrupted commits. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.7.2-beta.5 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.