OpenClaw v2026.5.2-beta.2: Gateway startup, session listing, task maintenance, delivery notes

v2026.5.2-beta.2 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.

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

The operator question around External plugin installation now covers diagnostics is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

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.

Use Control UI and WebChat reliability improves 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.

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.

Channel and provider fixes cover Telegram topic commands 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.

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.

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

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.

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

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.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising External plugin installation now covers diagnostics.
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

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. Keep the reproduction and the post-fix result together in the acceptance record.

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. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.5.2-beta.2 release notes for the exact change list, then cross-check the official release index and the channel routing guide before acting.