OpenClaw v2026.3.22-beta.1: ClawHub/install, interface notes

v2026.3.22-beta.1 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 / ClawHub/install

Source signal. add native openclaw skills search|install|update flows plus openclaw plugins install clawhub:<package> with tracked update metadata, gateway skill-install/update support for ClawHub-backed requests, and regression coverage/docs for the new source path.

The acceptance test for ClawHub/install is idempotence under interruption: start once, stop the transport, resume, and compare the final record with the original request.

02 / Plugins/marketplaces

Source signal. add Claude marketplace registry resolution, plugin@marketplace installs, marketplace listing, and update support, plus Docker E2E coverage for local and official marketplace flows.

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

03 / Commands/plugins

Source signal. add owner-gated /plugins and /plugin chat commands for plugin list/show and enable/disable flows, alongside explicit commands.plugins config gating.

For Commands/plugins, 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.

04 / Web tools/search provider lists

Source signal. keep onboarding, configure, and docs provider lists alphabetical while preserving the separate runtime auto-detect precedence used for credential-based provider selection.

Treat Web tools/search provider lists as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

The wiring behind the screen

Media/Windows security

block remote-host file:// media URLs and UNC/network paths before local filesystem resolution in core media loading and adjacent prompt/sandbox attachment seams, so the next release no longer allows structured local-media inputs to trigger outbound SMB credential handshakes on Windows.

The useful evidence for Media/Windows security is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to ClawHub/install.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Ask the same small question through the affected route and record the account, model id, context, and response time.
4. Compare the answer, tool permissions, and fallback behavior with the baseline before changing a default.
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

Web tools/search provider lists. keep onboarding, configure, and docs provider lists alphabetical while preserving the separate runtime auto-detect precedence used for credential-based provider selection. Record the failure that this correction addresses before declaring the upgrade complete.

Media/Windows security. block remote-host file:// media URLs and UNC/network paths before local filesystem resolution in core media loading and adjacent prompt/sandbox attachment seams, so the next release no longer allows structured local-media inputs to trigger outbound SMB credential handshakes on Windows. This is the edge case to include in a regression check, especially when the release is pre-release.

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