OpenClaw v2026.5.3-beta.2: Plugins/install, interface notes

v2026.5.3-beta.2 changes a surface that users can see. The release record describes a skills, plugin, marketplace, or SDK 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 / Plugins/file-transfer

Source signal. add bundled file-transfer plugin with file_fetch, dir_list, dir_fetch, and file_write agent tools for binary file ops on paired nodes; default-deny per-node path policy under plugins.entries.file-transfer.config.nodes with operator approval, symlink traversal refused by default (opt-in followSymlinks), and a 16 MB byte ceiling per round-trip.

Before widening access for Plugins/file-transfer, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

02 / Plugins/install

Source signal. harden official plugin install, uninstall, update, onboarding, ClawHub fallback, npm dependency-state reporting, and beta-channel update paths so externalized plugins behave like first-class package installs.

Plugins/install lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

03 / Gateway/performance

Source signal. trim startup and Control UI hot paths by lazy-loading plugin/runtime discovery, cron, schema, shutdown, sessions, and model metadata work only when needed.

Check Gateway/performance 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.

04 / Channels/replies

Source signal. improve Discord status reactions and degraded transport reporting, add WhatsApp Channel/Newsletter targets, and tighten Telegram, Feishu, Matrix, Microsoft Teams, and Slack delivery/recovery behavior.

For Channels/replies, 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 wiring behind the screen

Install/update

recover broken macOS LaunchAgent upgrades, reject source-only plugin packages before runtime load, and repair stale Gateway/plugin state during updates and doctor runs.

A successful click does not establish Install/update. Compare the state before and after a reload, then verify that a user can tell what happened without reading internal logs.

Plugins/onboarding

let Manual setup install optional official plugins, including ClawHub-backed diagnostics with npm fallback, and expose the external Codex plugin as a selectable provider setup choice.

Check Plugins/onboarding 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.

Plugins/CLI/update

include package dependency install state in openclaw plugins list --json, try plugin @beta updates first on the beta OpenClaw channel, and fall back to default/latest when no plugin beta release exists.

For Plugins/CLI/update, 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.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Plugins/file-transfer.
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

Plugins/update. keep beta-installed OpenClaw package updates on the beta plugin channel even when config still says stable, so Discord and other externalized plugins update from compiled @beta packages instead of stale source-only latest artifacts. Record the failure that this correction addresses before declaring the upgrade complete.

Agents/tools. stop treating tools.deny: ["write"] as an implicit apply_patch deny; operators who want to block patch writes should deny apply_patch or group:fs explicitly. Fixes #76749. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.5.3-beta.2 GitHub release. The release index gives the surrounding sequence, while the skills documentation supplies the operational background.