OpenClaw v2026.5.26: Safer content boundaries, for maintainers

For maintainers reading v2026.5.26, the source is a map of contracts. It describes a channel, client, interface, or browser change, then lists implementation changes and fixes that can affect plugins, providers, or downstream tooling.

Stable status describes the release line, not every local provider or channel. Check the version-specific notes before upgrading. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Compatibility for maintainers

Faster Gateway and replies

What changed. startup avoids repeated plugin, channel, session, usage-cost, warning, scheduled-service, and filesystem scans; visible replies separate user-facing sends from slower follow-up work; Gateway runtime/session caches churn less under load.

Check it with. Faster Gateway and replies 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.

Transcripts are core

What changed. transcript-backed meeting summaries, source-provider chunks, cleaned user turns, media provenance, Codex mirrors, WebChat replies, and CLI/TUI replay now use one more reliable transcript path.

Check it with. A catalog label for Transcripts are core is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

More channels are production-ready

What changed. Telegram keeps typing/progress context and forum topics, iMessage handles attachment roots, remote media staging, and duplicate local Messages sources, WhatsApp restores group/media behavior, Discord improves voice playback and model picking, and Signal/iMessage/WhatsApp get reaction approvals.

Check it with. The useful evidence for More channels are production-ready is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Better voice and Talk

What changed. realtime Talk runs can be inspected, steered, cancelled, or followed up from Web UI and Discord voice; wake-name handling is more tolerant without letting ambient speech trigger agents.

Check it with. Use Better voice and Talk 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.

API, package, and test clues

Safer content boundaries

Browser snapshot reads honor SSRF policy, system-event text cannot spoof nested prompt markers, fetched file text is wrapped as external content, ClickClack inbound sender allowlists run before agent dispatch, stale device tokens are rejected, and serialized tool-call text is scrubbed from replies.

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

Transcripts

add core transcript capture and source-provider support for transcript-backed meeting summaries, including the renamed Transcripts docs, CLI surface, source-provider chunks, and cleaned user-turn persistence.

Transcripts changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Auth

add named model login profiles and supported credential migration for Hermes, OpenCode, and Codex auth profiles, with explicit opt-out and non-interactive controls.

The useful evidence for Auth is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

Run the smallest useful rehearsal

1. Write down the baseline for Faster Gateway and replies, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw security audit

Leave a usable maintenance note

Save the command, output, source link, and environment used for this check. Future operators should be able to tell whether a difference belongs to the release or to local provider, channel, or platform state.

Fix details to carry forward

Memory/security. reject prompt-like text submitted through the explicit memory_store tool before embedding or storage, matching the existing auto-capture prompt-injection filter. This is the edge case to include in a regression check, especially when the release is pre-release.

Gateway/security. enable the default auth rate limiter for remote non-browser and HTTP gateway auth failures when gateway.auth.rateLimit is unset, while preserving the loopback exemption. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.5.26 notes with your test result. Read the official release index for neighboring versions and the channel routing guide for configuration limits.