header-langage
简体中文
繁體中文
English
Tiếng Việt
한국어
日本語
ภาษาไทย
Türkçe
Scan to Download the APP

OpenClaw released v2026.5.2: Plugin Migration from npm to ClawHub

According to Dynamic Insight Beating monitoring, the open-source personal AI assistant OpenClaw has released v2026.5.2, a major engineering maintenance update. The core change is the beginning of the plugin system migration from npm to the in-house distribution platform ClawHub, along with the resolution of over 200 known issues.

Regarding the plugin migration, OpenClaw has introduced the ClawPack packaging format, and plugin installation and updates will now carry versioned artifact metadata. Currently, npm is still the default, and ClawHub is only enabled when the clawhub: prefix is explicitly specified, marking a transitional period. External plugins now support direct installation from Git repositories. ACPX and OpenTelemetry diagnostics have been split into separate packages and are no longer installed with the core.

In terms of performance, this version has focused on governing multiple hot paths. The plugin tool descriptor has introduced caching, the prompt preparation phase no longer reloads plugin runtimes repeatedly; the session list interface has switched to a lightweight cache index, preventing lag in large session repositories; the Gateway skips unnecessary authentication overlays at startup, reducing readiness latency.

A notable bug fix: the heartbeat scheduler previously did not handle process exit events correctly, causing the heartbeat configured for every 30 minutes to actually trigger every 10 seconds, with an event loop delay peak exceeding 6 seconds, resulting in unresponsive Control UI and TUI. The new version introduces a centralized cooling mechanism and a per-agent floodgate, limiting unexpected feedback loops to a maximum of 5 times every 60 seconds.

Other changes include: the default chat model for the xAI provider has been upgraded to Grok 4.3; the SDK has added the tools.invoke RPC interface; the scope of desensitization logging for sensitive fields such as payment credentials and API Keys has been expanded; various messaging channels like Discord, Telegram, Slack, WhatsApp, and Signal have seen dozens of fixes.

举报 Correction/Report
Correction/Report
Submit
Add Library
Visible to myself only
Public
Save
Choose Library
Add Library
Cancel
Finish