OpenClaw v2026.3.13-beta.1: Android/chat settings, delivery notes

v2026.3.13-beta.1 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

01 / Android/chat settings

Source signal. redesign the chat settings sheet with grouped device and media sections, refresh the Connect and Voice tabs, and tighten the chat composer/session header for a denser mobile layout.

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

02 / iOS/onboarding

Source signal. add a first-run welcome pager before gateway setup, stop auto-opening the QR scanner, and show /pair qr instructions on the connect step.

The visible promise in iOS/onboarding needs a continuity check. Use non-sensitive data, refresh midway, and confirm that the same work remains attached to the right session.

03 / Browser/existing-session

Source signal. add an official Chrome DevTools MCP attach mode for signed-in live Chrome sessions, with docs for chrome://inspect/#remote-debugging enablement and direct backlinks to Chrome's own setup guides.

For Browser/existing-session, 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.

04 / Dashboard/chat UI

Source signal. stop reloading full chat history on every live tool result in dashboard v2 so tool-heavy runs no longer trigger UI freeze/re-render storms while the final event still refreshes persisted history.

A successful click does not establish Dashboard/chat UI. Compare the state before and after a reload, then verify that a user can tell what happened without reading internal logs.

The less visible details

Ollama/reasoning visibility

stop promoting native thinking and reasoning fields into final assistant text so local reasoning models no longer leak internal thoughts in normal replies.

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

Operator checklist before rollout

1. Before touching persistent state, capture the version, host, provider, and workspace for Android/chat settings.
2. Read the linked release record and verify a backup whenever the change can alter configuration or session data.
3. Exercise the named capability with a non-sensitive prompt, including the fallback or refusal result if it occurs.
4. Force a timeout or provider fallback in a disposable session and verify that no side effect is repeated.
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 models

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

Dashboard/chat UI. stop reloading full chat history on every live tool result in dashboard v2 so tool-heavy runs no longer trigger UI freeze/re-render storms while the final event still refreshes persisted history. Treat the fix as a boundary condition and retain the source wording beside your local result.

Ollama/reasoning visibility. stop promoting native thinking and reasoning fields into final assistant text so local reasoning models no longer leak internal thoughts in normal replies. Keep the reproduction and the post-fix result together in the acceptance record.

This page is a practical reading of the v2026.3.13-beta.1 source record; the release index and existing browser session guide remain the references to use for migrations and support boundaries.