OpenClaw v2026.5.31-beta.3: Clearer cron and channel history, delivery notes

v2026.5.31-beta.3 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.

Follow the message path

Faster Control UI chat

What changed. transcript rendering, draft persistence, pending-send paint, scrolling, and first-message work no longer block one another while a conversation is active.

Check it with. The operator question around Faster Control UI chat is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

More reliable agent recovery

What changed. fallback auth state, legacy Codex app-server auth, stale bootstrap history, and streamed reasoning cleanup recover cleanly instead of carrying stale turn state forward.

Check it with. Before widening access for More reliable agent recovery, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

Clearer cron and channel history

What changed. external sessions_send routes, single-job history, and channel reply state retain the right destination and job context through restarts.

Check it with. Clearer cron and channel history 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.

Better operator coordination

What changed. core session goals and durable plugin-install state make long-running work easier to inspect and resume after reloads.

Check it with. The privacy boundary around Better operator coordination is visible in the negative case. Seed two disposable conversations, ask for each one separately, and confirm that neither crosses its owner or workspace.

The less visible details

Safer mobile reconnects

iOS realtime sessions retain their WebSocket continuation instead of failing a healthy Talk connection, with hosted push/realtime paths kept aligned.

For Safer mobile reconnects, inspect state rather than only the new control. Repeat the flow after reload and reconnect, and note the session, pending action, URL, and visible error.

Workboard task details, Android notification app

Workboard task details, Android notification app selection, and Dreaming candidate scoring gained broader operator controls.

The visible promise in Workboard task details, Android notification app needs a continuity check. Use non-sensitive data, refresh midway, and confirm that the same work remains attached to the right session.

Control UI now streams stable Markdown blocks

Control UI now streams stable Markdown blocks and records more chat responsiveness signals to guide first-reply performance work.

The visible promise in Control UI now streams stable Markdown blocks needs a continuity check. Use non-sensitive data, refresh midway, and confirm that the same work remains attached to the right session.

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Faster Control UI chat.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Interrupt one delivery after admission, reconnect the transport, and compare the final reply with the original conversation.
4. Force a short transport interruption and verify that retry or recovery preserves the original thread and sender.
5. 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

Chat/UI. keep first Control UI sends responsive, retain pending sends while history catches up, cache transcript renders, and avoid draft persistence or navigation churn from blocking the active conversation. Treat the fix as a boundary condition and retain the source wording beside your local result.

Agents/Codex/auth. repair automatic fallback state, accept supported legacy Codex app-server auth, remove stale bootstrap history, strip streamed reasoning tags, and validate shell snapshots against trusted environment data. Keep the reproduction and the post-fix result together in the acceptance record.

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