OpenClaw v2026.5.2-beta.3: Control UI and WebChat reliability improves, delivery notes

v2026.5.2-beta.3 is a channel and session story. The official source describes a channel, client, interface, or browser change, and the important question is what survives the handoff between a Gateway, a conversation, and a reconnect.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

Follow the message path

01 / External plugin installation now covers diagnostics

Source signal. External plugin installation now covers diagnostics, onboarding, doctor repair, channel setup, install/update records, and artifact metadata while keeping bare package installs on npm for the first cutover.

Use External plugin installation now covers diagnostics as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

02 / Gateway startup, session listing, task maintenance

Source signal. Gateway startup, session listing, task maintenance, prompt prep, plugin loading, and filesystem hot paths get targeted cache and fanout reductions for large or plugin-heavy installs.

For Gateway startup, session listing, task maintenance, 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 / Control UI and WebChat reliability improves

Source signal. Control UI and WebChat reliability improves across Sessions, Cron, long-running Gateway WebSockets, grouped-message width, slash-command feedback, iOS PWA bounds, selection contrast, and Talk diagnostics.

The operator question around Control UI and WebChat reliability improves is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

04 / Channel and provider fixes cover Telegram topic commands

Source signal. Channel and provider fixes cover Telegram topic commands and networking, Discord delivery and startup edge cases, OpenAI-compatible TTS/Realtime, OpenRouter/DeepSeek replay, Anthropic-compatible streaming, Brave/SearXNG/Firecrawl web search, and voice-call routing.

The operator question around Channel and provider fixes cover Telegram topic commands is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

The less visible details

Gateway/startup

skip plugin-backed auth-profile overlays during startup secrets preflight, reducing gateway readiness latency while keeping reload and OAuth recovery paths overlay-capable.

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

Plugins/ClawHub

make diagnostics, onboarding, doctor repair, and channel setup carry ClawPack metadata through install records while keeping explicit clawhub: installs on ClawHub and bare package installs on npm for the launch cutover.

Plugins/ClawHub 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.

Plugins/CLI

include package dependency install state in openclaw plugins list --json so scripts can spot missing plugin dependencies without runtime-loading plugins.

The maintainer check for Plugins/CLI is a complete package review: identify the entry point, requested access, dependency tree, and uninstall behavior before publishing or upgrading.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for External plugin installation now covers diagnostics.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
4. Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
5. Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

Agents/OpenAI. default GPT-5 API-key sessions to the SSE Responses transport unless WebSocket is explicitly selected, restoring replies in fresh Control UI and WebChat beta installs where the auto WebSocket path connected but produced no model events. Treat the fix as a boundary condition and retain the source wording beside your local result.

Agents/sessions. preserve terminal lifecycle state when final run metadata persists from a stale in-memory snapshot, preventing sessions from staying stuck as running after completed or timed-out turns. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.5.2-beta.3 source record; the release index and channel routing guide remain the references to use for migrations and support boundaries.