OpenClaw 2026.6.2-beta.1: Operator Install Policy Replaces Dangerous-Code Scanner

OpenClaw’s June 3 beta, v2026.6.2-beta.1, ships a foundational security and reliability overhaul. The headline change: plugin and skill installs now use an operator install policy that replaces the old dangerous-code scanner path. This affects every install pathway — package, archive, source, upload, and marketplace — with clearer doctor checks, CLI wiring, and ClawHub metadata surfaces (#89516, thanks @joshavant).

Beyond install policy, this release tightens things across the board:

  • Channels: Telegram, Feishu, Discord, WhatsApp, and outbound delivery paths got safer around duplicate transcript mirrors, admin writeback, streamed-final previews, approval allowlists, setup runtime state, poll modifiers, Discord voice errors, and internal progress traces (#88973, #89626, #89812, #89035, #89814, #89813, #89601).
  • UI/Chat: Chat, Control UI, Skill Workshop, Workboard, Android companion shell, and WebChat flows now preserve visible streaming text, reconcile completed sends, expose ACK timing, add Workboard keyboard movement, harden dialog accessibility, lazy-load usage views, and improve Android companion-first shell navigation.
  • Security/policy: Corrupt shell snapshots, unsupported policy keys, unsafe exec approval precheck environments, malformed script limits, and suspicious gateway startup configs are now rejected. Data-handling conformance checks are added.
  • Gateway/memory: Session write-lock release failures, abandoned Codex app-server startups, stream-to-parent ACP spawns, custom-provider runtime fanout, bundled provider aliases, prompt-cache boundaries, Gemini stop sequences, Kimi cache markers, and watcher pressure warnings now recover cleanly.
  • Release/CI: Network calls are bounded, package hydration paths and Windows installer publishing are tighter, and release asset verification is now enforced.

The release is available on GitHub as a pre-release. Upgrade path: openclaw update --channel stable or pull the latest Docker image.

← Back to News