Guide

OpenClaw v2026.5.28-beta.2: Channel delivery and session identity got safer, recovery notes

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

v2026.5.28-beta.2 is easiest to understand through failure. The official record describes a provider, model, voice, or context change; the sections below spell out what to save, what to interrupt, and what must remain available afterward.

This candidate is still pre-release. Treat provider, channel, and migration behavior as unconfirmed until your own bounded test passes. Treat the version as one input to the decision. Local credentials, enabled plugins, channels, and host support still need their own evidence.

Channel
Pre-Release

Primary signals
Agent and Codex runtime recovery is steadier; Channel delivery and session identity got; Mobile and chat surfaces got a broader

Publication date
2026-05-29

Failure and recovery path

Agent and Codex runtime recovery is steadier

Evidence from the release. subagents keep cwd/workspace separation, hook context stays prompt-local, session locks release on timeout abort, stale restart continuations are avoided, and Codex app-server/helper failures no longer tear down shared runtime state.

Operator reading. The safe reading of Agent and Codex runtime recovery is steadier is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

Channel delivery and session identity got safer

Evidence from the release. Channel delivery and session identity got safer across outbound plugin hooks, Matrix room ids, iMessage reactions/approvals, Slack final replies, Discord recovered tool warnings, WhatsApp profile auth roots, Telegram polling, and Microsoft Teams service URL trust checks.

Operator reading. Read Channel delivery and session identity got safer as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Mobile and chat surfaces got a broader refresh

Evidence from the release. the iOS Pro UI, Gateway chat transport, onboarding, Talk permissions, WebChat reconnect delivery, and session picker behavior now preserve more state across reconnects and empty searches.

Operator reading. Before widening access for Mobile and chat surfaces got a broader refresh, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Browser, channel, and automation inputs are stricter

Evidence from the release. Browser tool timeouts, viewport/tab indices, Gateway ports, cron retry handling, Discord component ids, schema array refs, Telegram callback pages, and channel progress callbacks now reject malformed values earlier and preserve the intended delivery context.

Operator reading. The operator question around Browser, channel, and automation inputs are stricter is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

The limits of the recovery promise

Provider, media, and document coverage expands

Provider, media, and document coverage expands with Claude Opus 4.8, Fal Krea image schemas, NVIDIA featured models, MiniMax streaming music responses, encrypted PDF extraction, voice model catalogs, GitHub Copilot agent runtime support, and a Codex Supervisor plugin path for delegated Codex workflows.

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

Status

show active subagent details in status output.

A release note about Status becomes useful when the same task can be repeated after a restart and still produce an explainable result.

Diffs

split the default language pack and expand default Diffs language coverage while keeping the host floor aligned.

Use Diffs for a small reproducible task: save the input, visible result, useful failure, and version context another operator would need.

Run the smallest useful rehearsal

Write down the baseline for Agent and Codex runtime recovery is steadier, including the installed version, host, provider, and workspace.
Confirm what can be restored, then take a verified backup before applying the candidate package.
Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
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

Agents. fall back to local config pruning when the optional agents delete Gateway probe cannot authenticate, so offline installs can still delete agents without removing shared workspaces. This is the edge case to include in a regression check, especially when the release is pre-release.

Tighten phone-control mutation authorization [AI]. The release records a focused fix in tighten phone-control mutation authorization [ai]. Treat the fix as a boundary condition and retain the source wording beside your local result.

Keep the full v2026.5.28-beta.2 notes with your test result. Read the official release index for neighboring versions and the model provider reference for configuration limits.