OpenClaw v2026.7.2-beta.3: Safer channel operation, delivery notes

v2026.7.2-beta.3 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

Remote coding sessions

What changed. run Control UI sessions on cloud workers, open Codex and Claude catalog sessions in terminals on their owning hosts, and resume OpenCode and Pi sessions directly in a terminal.

Check it with. A catalog label for Remote coding sessions is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

Native automation and nodes

What changed. bring Automations parity to mobile, add foreground Voice Wake on Android, and expose camera, location, and notification capabilities from headless Linux nodes.

Check it with. Check Native automation and nodes with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Safer channel operation

What changed. prevent Telegram durable-ingress loss after restarts, keep Signal stop and approval controls responsive during active turns, and stop channel allowlists from granting owner access.

Check it with. Read Safer channel operation as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Guided Control UI setup

What changed. configure model providers from Settings, onboard channels through a guided setup page, and choose images and models while creating sessions.

Check it with. For Guided Control UI setup, 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.

The less visible details

Gateway and session recovery

prevent restart admission from wedging the Gateway, recover reply sessions after finalization stalls, and keep one-shot cron jobs enabled through lifecycle claim races.

For Gateway and session recovery, write down the owner and retry boundary before running anything. Repeat the trigger and check that recovery does not create a second message, job, or file.

External gateway supervision

add OPENCLAW_SUPERVISOR_MODE=external for lifecycle owners such as OCM, preserving verified restart and deferral behavior without exposing native service authority, blocking native service mutation and self-update, and providing a versioned atomic restart-handoff consume contract.

Before widening access for External gateway supervision, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

ClickClack guided setup

configure ClickClack from openclaw onboard or openclaw channels add clickclack with URL, token, and workspace prompts, default-account env fallback, nonfatal live connection validation, and gateway-aware next steps that connect automatically when OpenClaw is already running.

Use ClickClack guided setup as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Remote coding sessions.
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

Cloud worker derived workspace caches. exclude Python caches, dependency trees, and macOS metadata symmetrically from outbound sync and inbound reconciliation so local cache rewrites cannot fence later cloud results or worker reclaim. Keep the reproduction and the post-fix result together in the acceptance record.

Codex model status diagnostics. report a configured Codex route as unavailable when its harness plugin is disabled, missing, or quarantined, while preserving the separate credential result and making models status --check fail instead of silently treating fallback execution as healthy. Record the failure that this correction addresses before declaring the upgrade complete.

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