OpenClaw v2026.5.3-beta.3 Release: Enhanced Agent Capabilities, Performance, and Reliability

The OpenClaw v2026.5.3-beta.3 release brings a host of significant enhancements and critical fixes, focusing on expanding agent capabilities, improving platform performance, and bolstering overall reliability.

Key Changes

New File Transfer Plugin

A major highlight is the introduction of a bundled file-transfer plugin. This new plugin equips agents with powerful tools for binary file operations on paired nodes, including file_fetch, dir_list, dir_fetch, and file_write. Security is paramount, with a default-deny per-node path policy that requires operator approval, refusal of symlink traversal (opt-in followSymlinks), and a 16 MB byte ceiling per round-trip. This opens up new possibilities for agents to interact with file systems securely and effectively.

Performance and Reliability Boosts

The Gateway and Control UI hot paths have been significantly trimmed by lazy-loading plugin/runtime discovery, cron, schema, shutdown, sessions, and model metadata. This means faster startup times and a more responsive user interface. Agent runtime reliability has also seen substantial improvements, preserving streamed provider replies, delayed A2A session replies, prompt/tool delivery, memory recall, web search provider discovery, and provider-specific thinking/model metadata across common edge cases.

Hardened Plugin Management

Official plugin installation, uninstallation, updates, onboarding, ClawHub fallback, npm dependency-state reporting, and beta-channel update paths have been hardened. Externalized plugins now behave like first-class package installs, ensuring a smoother and more secure plugin lifecycle. This includes fixes for broken macOS LaunchAgent upgrades and the repair of stale Gateway/plugin state during updates and doctor runs.

Enhanced Channel Capabilities

Communication channels receive several upgrades:

• Unified Streaming Drafts: A new streaming.mode: "progress" introduces unified drafts with auto single-word status labels and shared progress configuration across Discord, Telegram, Matrix, Slack, and Microsoft Teams.
• New Targets: WhatsApp Channel/Newsletter targets have been added, expanding outbound communication options.
• Improved Delivery: Telegram, Feishu, Matrix, Microsoft Teams, and Slack delivery and recovery behaviors have been tightened for greater reliability. Discord status reactions now allow explicit tool calls to track subsequent tool progress.

Agent Interaction and Tooling

• Direct Session Steering: A new /steer <message> command allows for queue-independent steering of the active current-session run without initiating a new turn when the session is idle.
• BTW Alias: The /side command has been added as a text and native slash-command alias for /btw side questions.
• Smart Tool Loading: Optional media and PDF tool factories are now skipped when the effective tool denylist already blocks them, avoiding unnecessary hot-path setup for tools that will be filtered out before model use.

Configuration and Diagnostics

The doctor --fix command is now more robust, committing safe legacy migrations even when unrelated validation issues prevent full validation from passing. This ensures that agents.defaults.llm and other known-legacy keys are always cleaned up. Invalid Gateway configuration now fails closed, with openclaw doctor --fix owning the last-known-good repair, preventing unexpected behavior from bad config.

Impact

This release significantly enhances the OpenClaw platform across several dimensions, delivering a more powerful, reliable, and user-friendly experience.

For Developers and Operators:

• Streamlined Operations: The lazy-loading performance improvements mean faster deployments and more responsive interactions with the Control UI. Hardened plugin management simplifies the lifecycle of external plugins, making them more predictable and secure.
• Robust Diagnostics and Recovery: doctor --fix is now a more effective tool for maintaining configuration health, especially in complex upgrade scenarios. The new shell command explainer lays groundwork for improved command review and approval processes.
• Enhanced Security Posture: The file-transfer plugin's granular policy controls, coupled with hardened plugin installs and network proxy guards, provide a stronger security foundation for agent operations.

For Agents and End-Users:

• More Capable Agents: Agents can now perform binary file operations, opening up new use cases in data management, content delivery, and automated system interactions. The /steer command offers more immediate control, allowing users to guide ongoing agent tasks without interruption.
• Improved Local LLM Reliability: A critical fix addresses issues where local Ollama LLMs would produce "nonsense" output due to context truncation. As one user vividly described:

  So I fixed it [the timeout], and the local LLM still act like a moron. This fix ensures that catalog-driven context windows are correctly forwarded, restoring precise tool selection and coherent responses for local models.

• Consistent and Reliable Interactions: Unified streaming progress across various channels provides a smoother experience during long agent responses. Improved delivery and recovery mechanisms for channels like Telegram and Slack mean fewer dropped messages and more consistent communication.
• Smoother Upgrades: Fixes for macOS LaunchAgent and plugin state during updates aim to reduce friction and ensure a more seamless upgrade path.

Upgrade Guide

This release includes several changes that may require user action or awareness during the upgrade process.

Breaking Changes and Required Migrations

• Invalid Configuration Handling: The Gateway will no longer auto-restore invalid configuration during startup or hot reload. Instead, invalid config will cause the Gateway to fail closed. Users must run openclaw doctor --fix to repair any invalid configuration after upgrading. This ensures that the system operates with a valid configuration.
• tools.deny Behavior for apply_patch: The behavior of tools.deny: ["write"] has changed. It no longer implicitly denies apply_patch. If your configuration relied on tools.deny: ["write"] to block apply_patch, you must now explicitly deny apply_patch or the group:fs tool group in your tools.deny list.
• Legacy Streaming Configuration: If you have legacy streaming.progress configuration in your channel settings, doctor --fix will migrate it to streaming.preview.toolProgress. It is recommended to run openclaw doctor --fix after upgrading to ensure your configuration is up-to-date.
• Boolean messages.visibleReplies: Boolean values for messages.visibleReplies and messages.groupChat.visibleReplies will now be coerced to documented enum modes. While doctor --fix should handle this safely, reviewing your configuration after upgrade is advised.

Recommended Post-Upgrade Actions

• Run openclaw doctor --fix: This is strongly recommended for all users after upgrading. It will:
  • Migrate legacy sandbox container and browser registry files to the new sharded format.
  • Clean up deprecated configuration keys like agents.defaults.llm.
  • Repair stale Gateway and plugin state, particularly for macOS LaunchAgent setups.
• Reconcile Plugin Installs: If you experienced issues with multiple @openclaw/* sibling plugins overwriting each other during installation in previous versions, running openclaw plugins update --all or openclaw doctor --fix will now correctly reconcile and ensure all registered plugins are present on disk.
• WhatsApp Users (pnpm v9+): The fix for @whiskeysockets/libsignal-node in onlyBuiltDependencies addresses an issue with pnpm v9+ blockExoticSubdeps. If you use pnpm v9+ and WhatsApp, this issue should now be resolved.