OpenClaw v2026.5.26-beta.1: Faster replies and startup, upgrade notes

v2026.5.26-beta.1 arrived on 2026-05-26 with a change that matters during maintenance: faster replies and startup. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Before the package changes

01 / Faster replies and startup

Source signal. visible reply delivery now separates user-facing sends from slower follow-up work, command/model/plugin metadata is reused on hot paths, and Gateway startup avoids repeated plugin, channel, session, usage-cost, and filesystem scans.

The operator question around Faster replies and startup is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

02 / Better voice and Talk

Source signal. 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.

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.

03 / More channels are production-ready

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

Treat More channels are production-ready as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

04 / Safer agents

Source signal. Codex app-server auth, compaction, source replies, sandbox path handling, and usage-limit recovery are more robust; OpenAI-compatible providers avoid empty-tool and malformed payload failures.

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

Details behind the headline

More reliable replay and installs

legacy tool results, subagent spawn payloads, stale lock ownership, Windows stack-heavy startup, macOS restart validation, and Docker package preparation all fail less surprisingly.

Test More reliable replay and installs at the edges of the interface: clean start, reload, reconnect, and a refused or unavailable action. Keep the final screen and error message with the release note.

Transcripts

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

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.

Read Auth as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Faster replies and startup.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
4. Compare the transcript before and after reconnect, including delivery state and any visible error.
5. 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

Reply/perf. reduce visible reply delivery latency by preserving Telegram typing/progress context, lazy-loading slash-command startup metadata, avoiding hot-path model hydration, flag-gating Codex profiler timing, deferring context compaction maintenance, and tracking delivery timing. Keep the reproduction and the post-fix result together in the acceptance record.

Reply/source delivery. keep TUI, Control UI, media, TTS, transcript, and Codex source-reply finals live without duplicate terminal events or stale replay artifacts. Record the failure that this correction addresses before declaring the upgrade complete.

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