OpenClaw v2026.6.2-beta.1: Governed plugin and skill installs, interface notes

v2026.6.2-beta.1 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

01 / Governed plugin and skill installs

Source signal. the old dangerous-code scanner gives way to an operator install policy with clearer doctor, CLI, ClawHub, package, archive, source, upload, and marketplace recovery paths.

Use Governed plugin and skill installs to test ownership as well as installation. Confirm which agent owns the skill or plugin and that a missing or rejected package cannot mutate another workspace.

02 / Safer channel delivery

Source signal. Telegram, Feishu, Discord, WhatsApp, and outbound sends now handle transcript mirroring, streamed finals, admin writeback, approval allowlists, poll modifiers, and setup state without corrupting delivery.

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

03 / Steadier chat and operator UI

Source signal. visible stream text, completed sends, Workboard keyboard navigation, dialog accessibility, lazy usage views, and Android companion flows retain their state through normal interaction.

The visible promise in Steadier chat and operator UI needs a continuity check. Use non-sensitive data, refresh midway, and confirm that the same work remains attached to the right session.

04 / Stricter safety checks

Source signal. config, policy, shell snapshots, exec prechecks, script limits, and Gateway startup reject malformed or unsafe input before it becomes runtime state.

Keep Stricter safety checks measurable: name the input, expected output, failure signal, and operator who approved the test before calling the change ready.

The wiring behind the screen

More reliable Gateway and model sessions

session locks, abandoned Codex startup, ACP handoffs, custom-provider fanout, provider aliases, prompt caching, and memory checks recover without leaving a run wedged.

A catalog label for More reliable Gateway and model sessions is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

Plugins/security

replace dangerous-code scanner enforcement with operator install policy, install-policy context, doctor checks, install/update CLI wiring, ClawHub metadata paths, and package/archive/source/upload lifecycle coverage.

Treat Plugins/security as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Policy

add data-handling conformance checks and reject unsupported policy keys.

Use Policy for a small reproducible task: save the input, visible result, useful failure, and version context another operator would need.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Governed plugin and skill installs.
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

Channels/outbound. keep channel sends durable when transcript mirroring fails, stop schema-padded poll modifiers from blocking normal sends, preserve WebChat sessions_send handoffs, preserve Discord channel-label suppression while hiding internal agent failure traces, match Discord libopus error shapes, and sanitize Discord tool progress scaffolding. Record the failure that this correction addresses before declaring the upgrade complete.

Telegram/Feishu. require admin rights for Telegram target writeback, keep Telegram DM exec approval allowlists working with ask:off, prevent Telegram preview duplication across streaming modes, isolate verbose status after streamed finals, cancel clean restart stop timers, slow polling restart storms, and wire Feishu setup runtime setters. This is the edge case to include in a regression check, especially when the release is pre-release.

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