OpenClaw v2026.7.2-beta.1: Remote coding sessions, for maintainers

For maintainers reading v2026.7.2-beta.1, 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.

Compatibility for maintainers

01 / Remote coding sessions

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

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

02 / Native automation and nodes

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

The safe reading of Native automation and nodes is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

03 / Safer channel operation

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

Treat Safer channel operation as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

04 / Guided Control UI setup

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

Use Guided Control UI 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.

API, package, and test clues

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.

Keep Gateway and session recovery inside a test workspace until you can inspect its ledger, next run, failure state, and cancellation behavior from the operator surface.

Cloud workers

add session placement, dispatch, and worker-turn routing for remote session execution.

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

Paired-node coding agents

discover OpenCode and Pi sessions and continue Codex and Claude catalog sessions through streaming CLI agent runs.

Paired-node coding agents changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Run the smallest useful rehearsal

1. Write down the baseline for Remote coding sessions, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. 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

Terminal sessions. preserve early keystrokes, enable paired-node terminal actions, authorize paired-node catalog reads, recover after stale Control UI connections, and keep slow clients attached under heavy output. This is the edge case to include in a regression check, especially when the release is pre-release.

Control UI configuration. auto-save validated edits, restore autosave gates, show unapplied-restart state, and keep normal content scrolling and selection behavior. Treat the fix as a boundary condition and retain the source wording beside your local result.

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