OpenClaw v2026.5.3-beta.3: Performance, delivery notes

v2026.5.3-beta.3 is a channel and session story. The official source describes a skills, plugin, marketplace, or SDK change, and the important question is what survives the handoff between a Gateway, a conversation, and a reconnect.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Follow the message path

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.

The useful evidence for Plugins/file-transfer is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

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.

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

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.

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

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 less visible details

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.

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

Channels/streaming

add unified streaming.mode: "progress" drafts with auto single-word status labels and shared progress configuration across Discord, Telegram, Matrix, Slack, and Microsoft Teams.

Channels/streaming 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.

Agents/commands

add /steer <message> for queue-independent steering of the active current-session run without starting a new turn when the session is idle.

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

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Plugins/file-transfer.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
4. Compare the transcript before and after reconnect, including delivery state and any visible error.
5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Channels/WhatsApp. allow @whiskeysockets/libsignal-node in onlyBuiltDependencies so pnpm v9+ blockExoticSubdeps no longer rejects the baileys git-tarball subdep and silences all inbound agent replies. Fixes #76539. Keep the reproduction and the post-fix result together in the acceptance record.

Gateway/systemd. preserve operator-added secrets in the Gateway env file across re-stage while clearing OpenClaw-managed keys (such as OPENCLAW_GATEWAY_TOKEN) so a fresh staging value is never shadowed by a stale env-file copy; operator secrets are also retained when the state-dir .env is empty. Fixes #76860. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.5.3-beta.3 release notes for the exact change list, then cross-check the official release index and the skills documentation before acting.