releaseintermediate
[Release] openclaw/openclaw v2026.5.3: OpenClaw 2026.5.3
By steipetegithub
View original on githubOpenClaw v2026.5.3 introduces a bundled file-transfer plugin with secure binary file operations, hardens plugin installation workflows, and optimizes Gateway startup performance through lazy-loading. The release improves channel reliability across Discord, WhatsApp, Telegram, and other platforms, adds new agent steering commands, and fixes critical issues in realtime transcription, plugin updates, and systemd secret management.
Key Points
- •New file-transfer plugin provides `file_fetch`, `dir_list`, `dir_fetch`, and `file_write` tools with default-deny per-node path policies, symlink traversal protection, and 16 MB per-round-trip limits
- •Plugin installation hardened: official plugins now behave as first-class packages with improved npm dependency reporting, ClawHub fallback, and beta-channel update paths
- •Gateway startup optimized via lazy-loading of plugin discovery, cron, schema, sessions, and model metadata—only loaded when needed
- •New `/steer <message>` command enables queue-independent steering of active session runs without starting new turns when idle
- •WhatsApp Channel now supports explicit `@newsletter` outbound targets with channel session metadata instead of DM routing
- •Discord status reactions improved with unified `streaming.mode: "progress"` drafts and shared progress configuration across multiple channels
- •`doctor --fix` now commits safe legacy migrations even when unrelated validation issues exist, ensuring config cleanup regardless of other problems
- •Realtime transcription fixed: socket closes before provider readiness now correctly reported as closed-before-ready failures instead of connection timeouts
- •Gateway systemd integration preserves operator-added secrets across re-staging while clearing OpenClaw-managed keys to prevent stale env-file shadowing
- •Sandbox container and browser registry entries now stored as per-runtime shard files to reduce session lock contention during doctor migrations
Found this useful? Add it to a playbook for a step-by-step implementation guide.
Workflow Diagram
Start Process
Step A
Step B
Step C
Complete