Tutorial

OpenClaw v2026.5.26-beta.2: Transcripts are core, delivery notes

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

v2026.5.26-beta.2 is a channel and session story. The official source describes a channel, client, interface, or browser change, and the important question is what survives the handoff between a Gateway, a conversation, and a reconnect.

Pre-release status matters here: stage the tag beside the stable package and do not infer support for every account or platform. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.

Channel
Pre-Release

Primary signals
Faster Gateway and replies; Transcripts are core; More channels are production-ready

Publication date
2026-05-27

Follow the message path

Faster Gateway and replies

Evidence from the release. 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.

Operator reading. For Faster Gateway and replies, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

Transcripts are core

Evidence from the release. 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.

Operator reading. Check Transcripts are core with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

More channels are production-ready

Evidence from the release. 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.

Operator reading. 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

Evidence from the release. 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.

Operator reading. The operator question around Better voice and Talk is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

The less visible details

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.

Treat Safer content boundaries as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

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.

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

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.

Treat Auth as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Operator checklist before rollout

Before touching persistent state, capture the version, host, provider, and workspace for Faster Gateway and replies.
Read the linked release record and verify a backup whenever the change can alter configuration or session data.
Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.

openclaw --version
openclaw gateway status
openclaw security audit

Keep the source trail attached

Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.

Regression cases from the source

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. Treat the fix as a boundary condition and retain the source wording beside your local result.

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. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.5.26-beta.2 source record; the release index and channel routing guide remain the references to use for migrations and support boundaries.