Guide

OpenClaw v2026.5.12: Gateway, browser, Slack, node pairing, sandbox, upgrade notes

May 14, 20265 min readUpdated September 11, 2026By OpenClawBlog Team

v2026.5.12 arrived on 2026-05-14 with a change that matters during maintenance: gateway, browser, slack, node pairing, sandbox. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is stable, but the direct notes still define its migrations, corrections, and package-specific limits. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Channel
Stable

Primary signals
Leaner installs; Telegram got much more resilient; Codex/OpenAI paths are smoother

Publication date
2026-05-14

Before the package changes

Leaner installs

Evidence from the release. WhatsApp, Slack, Amazon Bedrock, Anthropic Vertex, and related provider/plugin dependency cones moved out of the core runtime so installs only pull what you use.

Operator reading. Use Leaner installs as a routing test: capture the destination before the send, interrupt the transport, and verify that retry logic did not duplicate or redirect the response.

Telegram got much more resilient

Evidence from the release. isolated polling, durable local spooling, safer group-media handling, and preserved HTML/Markdown formatting in streamed and scheduled replies.

Operator reading. Telegram got much more resilient lives at the handoff between the Gateway and a conversation. Send one harmless message, reconnect once, and compare the account, thread, sender, and final transcript.

Codex/OpenAI paths are smoother

Evidence from the release. auth-profile-backed media tools, MCP server projection, context-engine thread rotation, and better app-server/runtime fallback behavior.

Operator reading. Treat Codex/OpenAI paths are smoother as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Plugin installs and updates are harder to wedge

Evidence from the release. Plugin installs and updates are harder to wedge, with pnpm 11 support, peer-dependency preservation, safer runtime scans, and source/git install fixes.

Operator reading. Use Plugin installs and updates are harder to wedge to test ownership as well as installation. Confirm which agent owns the skill or plugin and that a missing or rejected package cannot mutate another workspace.

Details behind the headline

Gateway, browser, Slack, node pairing, sandbox

Gateway, browser, Slack, node pairing, sandbox, and transcript paths picked up a broad security/provenance hardening pass.

Before widening access for Gateway, browser, Slack, node pairing, sandbox, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Amazon Bedrock

externalize the Bedrock and Bedrock Mantle provider packages so core installs no longer pull AWS SDK dependencies unless those providers are installed.

The safe reading of Amazon Bedrock is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

Plugins

externalize Slack, OpenShell sandbox, and Anthropic Vertex so their runtime dependency cones install only when those plugins are installed.

Before widening access for Plugins, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Test this release without widening the boundary

Note the current version, host, provider, and workspace before exercising Leaner installs.
Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
Send one harmless message through the named account and save the account, thread, and sender identifiers.
Compare the transcript before and after reconnect, including delivery state and any visible error.
Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Doctor/Codex. stop warning that the message tool is unavailable for source-reply paths where OpenClaw grants message at runtime, keeping update and doctor output aligned with the OpenAI happy path. Keep the reproduction and the post-fix result together in the acceptance record.

Channels/Weixin. bump the external Weixin catalog entry to @tencent-weixin/openclaw-weixin@2.4.3 with the matching package integrity. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.5.12 release notes for the exact change list, then cross-check the official release index and the model provider reference before acting.