OpenClaw v2026.5.2: External plugin installation, update, doctor repair, for maintainers

For maintainers reading v2026.5.2, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.

Stable status describes the release line, not every local provider or channel. Check the version-specific notes before upgrading. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Compatibility for maintainers

01 / External plugin installation, update, doctor repair

Source signal. External plugin installation, update, doctor repair, dependency reporting, and artifact metadata now cover the npm-first cutover, stale configured installs, missing package payloads, and beta-channel plugin fallback.

The operator question around External plugin installation, update, doctor repair 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 and agent hot paths are leaner across startup

Source signal. Gateway and agent hot paths are leaner across startup, session listing, task maintenance, prompt prep, plugin loading, tool descriptor planning, filesystem guards, and large runtime configs.

The acceptance test for Gateway and agent hot paths are leaner across startup is idempotence under interruption: start once, stop the transport, resume, and compare the final record with the original request.

03 / Control UI and WebChat are more resilient

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

Control UI and WebChat are more resilient 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.

04 / Messaging fixes cover WhatsApp Channel/Newsletter

Source signal. Messaging fixes cover WhatsApp Channel/Newsletter targets, Telegram topic commands and networking, Discord delivery/startup edge cases, Slack threads, Signal groups/media, and visible reply routing.

The operator question around Messaging fixes cover WhatsApp Channel/Newsletter is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

API, package, and test clues

Provider and media fixes cover OpenAI-compatible

Provider and media fixes cover OpenAI-compatible TTS/Realtime, OpenRouter/DeepSeek replay, Anthropic-compatible streaming, LM Studio reasoning metadata, Brave/SearXNG/Firecrawl web search, media paths, music, and voice-call routing.

The operator question around Provider and media fixes cover OpenAI-compatible is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

Gateway/startup and restart

skip plugin-backed auth-profile overlays during startup secrets preflight, reducing gateway readiness latency while keeping reload and OAuth recovery paths overlay-capable; add openclaw gateway restart --force and --wait <duration>, log active task run IDs before restart deferral timers, and report timeout restarts as explicit forced restarts.

Read Gateway/startup and restart 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.

Run the smallest useful rehearsal

1. Write down the baseline for External plugin installation, update, doctor repair, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw security audit

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Fix details to carry forward

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. This is the edge case to include in a regression check, especially when the release is pre-release.

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. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.5.2 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.