OpenClaw v2026.7.2-beta.2: Native automation and nodes, interface notes

v2026.7.2-beta.2 changes a surface that users can see. The release record describes a channel, client, interface, or browser change; this article follows the state behind the screen instead of treating a new button as proof that the workflow is complete.

Because this is a pre-release, use a disposable Gateway first and leave the stable version available for comparison. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

State that a reader can see

The wiring behind the screen

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.

Exercise Gateway and session recovery twice with a disposable trigger. The expected result is one side effect, a readable terminal state, and a cancellation path while work is still pending.

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.

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

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Remote coding sessions.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Use a disposable conversation for one send, one reconnect, and one retry; keep the destination identifiers with the result.
4. Leave the channel disabled after the test if its credentials or pairing were created only for this rehearsal.
5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

External supervisor restart health. accept device-identity policy closes only when the replacement gateway lock and listener PID agree, preventing OCM-managed restarts from timing out after a successful handoff. Record the failure that this correction addresses before declaring the upgrade complete.

ACPX cleanup process inspection. bound host process-table reads so stalled ps calls cannot hang gateway startup or session cleanup while retaining fail-closed ownership checks. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.7.2-beta.2 GitHub release. The release index gives the surrounding sequence, while the channel routing guide supplies the operational background.