OpenClaw 2026.5.22 正式版解读：性能热路径、Transcript 基础与文档体验升级

版本：OpenClaw 2026.5.22 正式版。定位：2026.5.22 正式版主要围绕 Gateway 性能热路径、Transcript 初始基础、文档与配置说明、渠道恢复和运行时安全做系统性打磨。

一句话看懂这个版本

2026.5.22 正式版主要围绕 Gateway 性能热路径、Transcript 初始基础、文档与配置说明、渠道恢复和运行时安全做系统性打磨。

核心更新速览

为什么这个正式版值得关注？

这次整理只看 npm 与官方 CHANGELOG 中的正式版本号，不纳入带预发布后缀或尚未对应正式包的顶部草稿。OpenClaw 2026.5.22 的价值不只是新增功能，而是把实际运行中的启动速度、渠道投递、权限边界、运行时恢复和多模型连接继续打磨得更稳。

官方 Changes 摘要

• Gateway/perf: reuse process-stable channel catalog reads, avoid repeated bundled-channel boundary checks, and rotate gateway watch CPU profiles so benchmark runs do not accumulate unbounded artifacts.
• Gateway/perf: reuse immutable plugin metadata snapshots across startup, config, model, channel, setup, and secret metadata readers so hot paths avoid repeated plugin file stats and manifest registry reloads.
• Gateway/perf: lazy-load startup-idle plugin work, core gateway method handlers, and the embedded ACPX runtime so Gateway health and ready signals no longer wait on unused handler trees or ACPX probes.
• Gateway/perf: cache plugin SDK public-surface alias maps and skip irrelevant macOS Linuxbrew PATH probes so Gateway startup avoids repeated filesystem walks and slow missing-directory stats.
• Transcripts: add the initial transcript capture and source-provider foundation, including auto-start capture config, manual transcript imports, read-only transcript access, and Discord voice as the first live source.
• Docs/channels/config: add Signal `configPath`, Telegram wildcard topic defaults, local-time backup archive names, Termux home fallback, include-path validation, secret-scanner-safe placeholder guidance, Gemini CLI/Antigravity media guidance, and macOS VM auto-login guidance.
• Docs: clarify model-usage portability, Codex migration prerequisites, status bootstrap wording, thread-bound subagent limits, hook ownership, and config-preserving safety guidance.
• Docs: clarify README onboarding and Gateway startup paths, WhatsApp QR/408 recovery, cron output language prompts, skill advanced features, gateway upstream 403 troubleshooting, and plugin fallback override guidance.

官方 Fixes 摘要

• WebChat: summarize internal message-tool source replies so tool cards no longer duplicate the visible reply body.
• Gateway: preserve deferred lifecycle-error cleanup across later non-terminal events so provider timeouts can persist failed session state instead of leaving sessions stuck running. (#85256, fixes #63819)
• Agents/subagents: report tool-only child progress during timeout summaries instead of showing no visible output.
• Telegram/ACP: preserve explicit `:topic:` conversation suffixes when inbound ACP targets do not carry a separate thread id.
• Browser/proxy: bypass the managed proxy for the exact local managed Chrome CDP readiness and DevTools WebSocket endpoints, so `openclaw browser start` works when the operator proxy blocks loopback egress.
• Ollama: bypass the managed proxy for configured local embedding origins while keeping SSRF guardrails on unconfigured targets.
• OpenAI/images: route Codex API-key image generation through the native OpenAI Images API instead of the Codex OAuth streaming backend, avoiding 401s from valid API keys.
• Agents/OpenAI completions: omit empty tool payload fields for proxy-like OpenAI-compatible endpoints so strict vLLM-style servers accept tool-free turns.

对用户的实际影响

• 更稳：多个修复都指向真实部署中的超时、恢复、缓存、队列和运行时状态问题。
• 更安全：工具调用、外部内容、认证、设备、渠道与执行审批边界更清楚。
• 更适合长期运行：Gateway、插件、Provider、Transcript 与渠道链路都在向生产级长期运行靠拢。
• 更容易排障：Doctor、日志、文档、CLI 和发布验证持续补齐，失败时更容易定位。

升级建议

如果你已经把 OpenClaw 接入多个聊天渠道、Cron 自动化、语音、Codex、插件或本地模型，建议优先阅读该版本说明并安排升级验证。若只是轻量体验，也可以先关注与自己相关的渠道和 Provider 修复。

写在最后

近期 OpenClaw 的更新方向很清晰：从“功能覆盖”继续走向“长期稳定、跨渠道可恢复、安全边界清晰”。这类正式版更新虽然不一定每条都显眼，但对日常可靠性很关键。

参考来源

• OpenClaw 官方 CHANGELOG：https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md
• OpenClaw GitHub Releases：https://github.com/openclaw/openclaw/releases
• OpenClaw npm package：https://www.npmjs.com/package/openclaw