update
May 3, 2026
By Teun
OpenClaw 2026.5.2 tightens plugins, gateway startup, and messaging
OpenClaw 2026.5.2 adds npm-first plugin handling, faster gateway startup paths, and a long list of fixes across control UI, messaging, providers, and sessions. The release also changes several defaults, including the xAI model catalog and how some Codex and Google Meet features behave.
OpenClaw 2026.5.2 focuses on plugin packaging, gateway startup, and a broad set of reliability fixes across messaging, sessions, and provider integrations.
The release changes how external plugins are installed and repaired during the npm-first cutover. According to the changelog, OpenClaw now carries ClawPack metadata through diagnostics, onboarding, doctor repair, and channel setup, while still keeping explicit clawhub: installs on ClawHub and bare package installs on npm for the launch transition. It also adds first-class git: plugin installs, support for plugin dependency state in openclaw plugins list --json, and beta-channel fallback behavior that tries @beta first and falls back to the default release when no beta plugin exists.
⚡ New to this?
This release is mainly about reliability and packaging changes. Plugins are add-ons that extend OpenClaw, and npm-first means the software is shifting more of that plugin delivery to npm, a common JavaScript package registry. It also fixes several places where sessions, channels, or UI screens could get stuck or report the wrong state.
🦞 OpenClaw angle
If you self-host OpenClaw, review your plugin inventory before and after upgrading. Use openclaw plugins list --json to spot missing dependencies, and check whether any external plugins now need npm, clawhub:, or git: installation paths.
If you rely on restart-sensitive automations, test Discord, Slack, Telegram, and WhatsApp flows after the upgrade, especially anything using threads, topic-bound sessions, or newsletter targets. Also run the new doctor repair path on a staging node first so stale plugin records and missing payloads are fixed before you roll the change into production.
OpenClaw also made startup and runtime paths leaner. The company said gateway startup now skips plugin-backed auth-profile overlays during secret preflight, which reduces readiness latency while preserving reload and OAuth recovery behavior. It also reused startup-loaded plugin registries at request time, memoized replay-policy resolution, and added a faster path for filesystem containment checks to cut repeated path work in hot walkers.
Several changes target the control UI and WebChat. OpenClaw said Sessions and Cron views are more resilient, long-running Gateway WebSockets now stay alive with protocol pings, and the iOS PWA view now respects safe-area bounds. The release also adds higher-contrast selection colors and inline feedback when local slash-command dispatch is unavailable or fails.
Messaging gets a long set of fixes. According to the changelog, WhatsApp now supports explicit @newsletter outbound targets, Telegram topic commands route correctly in bound sessions, Slack keeps bot-participated threads across restarts, Discord preserves active buttons and forms during Gateway restarts, and Signal groups and media paths are covered as well. The release also adds clearer visible reply routing and fixes several network and delivery edge cases.
On the provider side, OpenClaw added Grok 4.3 to the bundled catalog and made it the default xAI chat model. It also updated OpenAI-compatible text-to-speech endpoints to pass through extra request body fields, improved Anthropic-compatible streaming, and expanded fixes for OpenRouter, DeepSeek, LM Studio, Brave, SearXNG, and Firecrawl integrations.
Google Meet and voice-call handling also picked up new behavior. OpenClaw said API-created rooms can now set accessType and entryPointAccess, and it added googlemeet end-active-conference plus googlemeet test-listen to help close managed spaces and verify live caption movement before reporting listen-first health. The release also adds extra logging for Twilio Meet join phases and live-call debugging.
The update includes a one-time doctor repair for configured plugins on 2026.5.2, which updates stale plugin manifests, reinstalls missing configured plugins, and preserves unmanaged third-party plugin directories. It also adjusts session handling, transcript locks, gateway restart behavior, and several CLI and status commands to better reflect live state and avoid stale or misleading output.