OpenClaw v2026.5.2-beta.3: A Leap Forward in Performance, Reliability, and Plugin Integration

This beta release, v2026.5.2-beta.3, brings a significant focus on performance, reliability, and external plugin integration for OpenClaw. Key improvements span faster startup times, reduced resource consumption for large installations, enhanced stability across various channels and the Control UI, and a more robust external plugin ecosystem. This update is crucial for users seeking a more responsive and dependable agent orchestration platform, especially those with complex setups or heavy plugin usage.

Key Changes

• Enhanced External Plugin Management: A major highlight is the expanded support for external plugin installation, now covering diagnostics, onboarding, doctor repair, and channel setup. This allows for more flexible and metadata-rich plugin management through ClawHub, while still supporting bare package installs via npm for initial cutover. This includes externalizing components like ACPX and OpenTelemetry diagnostics into dedicated packages, reducing core dependencies. (Thanks @vincentkoc)
• Performance Optimizations: Significant effort has been put into reducing latency and resource usage. This includes skipping plugin-backed auth-profile overlays during gateway startup secrets preflight (#68327, thanks @JIRBOY), scoping broad runtime preloads to only effective plugin IDs, and reusing startup-loaded plugin registries for request-time providers and tools (thanks @DmitryPogodaev). Hot filesystem paths also benefit from faster POSIX containment checks (thanks @Enderfga).
• Improved Tooling and Agent Runtime: The agent runtime now memoizes transcript replay-policy resolution and caches plugin tool descriptors, allowing repeated prompt-time planning to skip plugin runtime loading while execution still loads the live plugin tool (#76079, thanks @shakkernerd). A new platform-level tool descriptor planner enhances visibility and availability checks.
• Control UI and WebChat Reliability: The user interface sees numerous stability enhancements, including improved session listing performance (#76051, thanks @Neomail2), better handling of long-running Gateway WebSockets (#70991, thanks @alexandre-leng), configurable grouped-message width (#67935, thanks @xiew4589-lang), and high-contrast text selection for accessibility (#60850, thanks @Badschaff, @efe-arv). iOS PWA bounds are now properly contained (#76072, thanks @kvncrw).
• Channel and Provider Updates:
  • Discord: Reliability improvements include keeping active buttons/selects/forms working across Gateway restarts, reusable message-channel access groups, and Discord channel-audience DM authorization (#75813, thanks @amknight). File upload capability is now discoverable by agents (#60652, thanks @claw-io, @efe-arv, @joelnishanth, @sjhddh).
  • Telegram: Fixes cover topic commands, networking robustness, and proper routing for native slash commands in bound top-level groups (#75405, thanks @ziptbm, @yfge).
  • OpenAI-compatible: Enhanced TTS/Realtime support, OpenRouter/DeepSeek replay, and Anthropic-compatible streaming fixes.
  • Web Search: Improvements for Brave, SearXNG, and Firecrawl, including baseUrl overrides and better error reporting for missing providers.
  • Google Meet: New API-created room access controls (accessType, entryPointAccess) and a command to end active conferences (#74824, thanks @BsnizND). Live caption health for Chrome transcribe mode is also added.
• New Features: Grok 4.3 is now in the bundled catalog and is the default xAI chat model. agents.defaults.skipOptionalBootstrapFiles allows skipping optional workspace files during bootstrap (#62110, thanks @mainstay22). First-class git: plugin installs are now supported, including ref checkout and update support.

Impact

This release addresses numerous pain points, making OpenClaw more robust, efficient, and user-friendly.

• Performance and Stability: Users with large or plugin-heavy installations will experience significantly faster startup times and reduced CPU load. The targeted caching and fanout reductions mean the Gateway remains responsive even under heavy load. The fix for redundant session store reads (#68554, thanks @henkterharmsel) is particularly impactful, as it prevents event loop blockages that could lead to plugin disconnects and outages.

  "On large sessions.json files this forces a synchronous readFileSync + JSON.parse on every write, blocking the Node.js event loop for seconds per call. Multiple queued calls cascade into 100+ second event loop blockages." - PR #68554

  This issue, causing Telegram plugin disconnects and gateway timeouts, is now resolved by removing unnecessary disk re-reads within session store locks. Similarly, task registry maintenance no longer causes quadratic CPU burn by repeatedly loading session stores (#73517, #75708, thanks @Lightningxxl, @glfruit, @jared-rebel).

• Improved Agent Reliability: Agents will benefit from more consistent context and tool execution. The fix for z.ai-style providers losing conversational context on consecutive turns (#76056, thanks @openperf) ensures agents maintain full history. Tool execution timeouts no longer trigger misleading LLM fallback errors, saving unnecessary cost and preventing task interruptions (#52147, #75873, thanks @simonusa).

• Enhanced User Experience: The Control UI and WebChat are more reliable and accessible. Issues like blank Control UI sections due to malformed cron rows (#55047) and unresponsive session listings (#76050, #76051, thanks @Neomail2) are resolved. High-contrast text selection (#60850, #60854, thanks @Badschaff, @efe-arv) improves accessibility for color-deficient users.

• Richer Channel Integrations:

  • Discord: Agents can now reliably discover and use file upload capabilities (#60652, #60808, #61087, #61100, thanks @claw-io, @efe-arv, @joelnishanth, @sjhddh). Previously, agents could create files but had no signal that Discord file delivery was supported.
  • Telegram: Commands now work correctly in forum topics and bound top-level groups, resolving silent command drops (#75405, #75558, #6457, thanks @ziptbm, @yfge, @dae-sun, @WouldenShyp).
  • BlueBubbles: An opt-in API fallback for reply context cache misses (#71820, thanks @coletebou, @zqchris) ensures agents maintain conversation context even after restarts or in multi-instance deployments.

• Security and Diagnostics: Critical security fixes include blocking untrusted workspace .env overrides for system paths and Python interpreters (#75940, #74492, #74463, thanks @pgondhi987). A new openclaw proxy validate command helps operators verify proxy configurations (#73438, thanks @jesse-merhi). Failed config backup restores are now correctly reported in logs and audit records (#70515, thanks @davidangularme), preventing silent configuration issues.

Upgrade Guide

This release includes some changes that may require user attention during upgrade.

1. Thread-Bound Session Spawning: The configuration for thread-bound session spawning has been simplified. The legacy subagent/ACP thread-spawn toggles are replaced with threadBindings.spawnSessions. By default, thread-bound spawns are now on.
   • Action: Users with existing configurations using the old toggles should run openclaw doctor --fix to migrate these legacy keys to the new threadBindings.spawnSessions format.
2. macOS LaunchAgent PATH Canonicalization: For macOS users, the Gateway LaunchAgent installation now uses a canonical system PATH (/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin) instead of preserving interactive-shell PATH entries that might include Node version managers (Volta, asdf, fnm, pnpm).
   • Impact: If your macOS Gateway service relied on shell PATH user directories for child tools, those tools may no longer be found by bare name.
   • Action: For any custom tools required by your Gateway service, configure explicit absolute paths or manage them via service-managed environment variables instead of relying on the interactive shell PATH. Running openclaw doctor --repair will apply this canonical PATH.
3. Blocked Workspace Environment Variables: Several environment variables related to system paths and Python interpreters (STATE_DIRECTORY, HOMEBREW_BREW_FILE, HOMEBREW_PREFIX, CLOUDSDK_PYTHON) are now explicitly blocked from being overridden by workspace .env files.
   • Impact: If you were using workspace .env files to set these variables, they will now be ignored for security reasons.
   • Action: For legitimate custom configurations, set these variables in your trusted global or process environment explicitly, rather than through workspace .env files.
4. Control UI Sessions Tab: The default query for the Control UI Sessions tab is now bounded to the last 120 minutes and a limit of 50 sessions to prevent expensive full-history scans on large session stores.
   • Impact: While this significantly improves UI responsiveness, if you need to view older or more numerous sessions by default, you will need to manually adjust the filters in the Sessions tab. The filters remain editable.
5. Google Meet API Room Access: New accessType and entryPointAccess controls for API-created Google Meet rooms have been added.
   • Action: If you use the googlemeet create command or the google_meet tool to create rooms and wish to utilize these new access controls, you may need to re-authorize with the meetings.space.settings OAuth scope.