openclaw 334056570 release notes / what's new

OpenClaw 334056570 delivers a transition to operator-controlled installation policies for plugins and skills, significant security hardening for channel integrations, and improved diagnostic visibility for gateway health.

Key Changes

Operator-Owned Install Policy

OpenClaw now replaces built-in dangerous-code scanners with a configurable operator install policy. Operators can define a trusted executable under security.installPolicy to make allow/block decisions for skill and plugin installations from sources including ClawHub, npm, Git, and local archives. This policy is fail-closed; any timeout, malformed JSON response, or non-zero exit from the policy executable will block the installation.

Security and Policy Hardening

Several critical security boundaries have been tightened:

• Node-Host Execution: Approval prechecks for node-host commands now use the forwarded node environment rather than the gateway-local PATH, preventing the gateway's environment from incorrectly satisfying a node allowlist precheck.
• Telegram Writeback: Telegram target resolution now requires operator.admin gateway scope to write back to user configuration or cron delivery targets.
• Telegram Execution: Fixed a bug where Telegram-origin natural-language execution could prompt for approval even when the effective policy was security=allowlist, ask=off and the command was allowlisted.
• Policy Validation: The policy.jsonc validation is now stricter, reporting unsupported policy sections or rule keys as policy/policy-jsonc-invalid instead of ignoring them.
• Data Handling Conformance: New data-handling policy checks allow operators to enforce redaction of sensitive logging, deny telemetry content capture, and restrict session transcript indexing into memory.

Channel and UI Improvements

• Outbound Delivery: Fixed a regression where schema-padded poll modifiers (e.g., pollDurationHours: 1) were incorrectly interpreted as poll intent, blocking routine send actions across all channels.
• Messaging Durability: Channel sends now remain durable even if transcript mirroring fails.
• Control UI: Added optional server-side ACK timing metadata for operator clients to distinguish between network request duration and server-side pre-ACK processing time.
• Telergam/Feishu: Improved handling of streamed finals, verbose status isolation, and setup runtime setters for Feishu.

System Stability and Diagnostics

• Gateway Health: The openclaw health and doctor commands now provide reachability-aware diagnostics when authentication is missing, replacing raw GatewayCredentialsRequiredError exceptions with clear guidance.
• Memory Management: Added a shared memory watcher-pressure warning helper to alert operators when large memory trees cause file descriptor pressure.
• Config Recovery: The gateway now recovers from suspicious-but-valid tiny config clobbers during startup snapshot reads.

Impact

For Operators

Operators must now define an install policy if they wish to control plugin and skill installations. The previous scan: false and force-unsafe bypass behaviors are retired. Diagnostic scanning remains available via openclaw security audit --deep.

For Users

Users of Telegram and Discord will experience more reliable message delivery and consistent approval behavior for allowlisted commands. Control UI users will see improved telemetry regarding message ACK timings.

For Developers

Plugin and skill developers should note that standalone plugin files installed via openclaw plugins install <file> are now rejected; managed local path installs now require plugin directories or archives with a manifest boundary. Standalone files should be configured via plugins.load.paths.

FAQ

What's new in 334056570? This release introduces an operator-owned install policy for plugins and skills, replaces dangerous-code scanners, hardens node-host and Telegram execution security, and improves gateway health diagnostics.

Are there any breaking changes? Yes. Built-in dangerous-code install scanners are removed. Managed CLI installs of standalone plugin files via openclaw plugins install <file> are now rejected in favor of directory or archive-based installs with manifests.

How do I upgrade? Upgrade via your package manager. After upgrading, use openclaw doctor --fix to remove stale scanner configuration residue.