OpenClaw v2026.3.11-beta.1: OpenRouter/models, recovery notes

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

Failure and recovery path

01 / OpenRouter/models

Source signal. add temporary Hunter Alpha and Healer Alpha entries to the built-in catalog so OpenRouter users can try the new free stealth models during their roughly one-week availability window.

Check OpenRouter/models 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.

02 / iOS/Home canvas

Source signal. add a bundled welcome screen with a live agent overview that refreshes on connect, reconnect, and foreground return, and move the compact connection pill off the top-left canvas overlay.

Test iOS/Home canvas 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.

03 / iOS/Home canvas

Source signal. replace floating controls with a docked toolbar, make the bundled home scaffold adapt to smaller phones, and open chat in the resolved main session instead of a synthetic ios session.

For iOS/Home canvas, 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 / Agents/text sanitization

Source signal. strip leaked model control tokens (<|...|> and full-width <｜...｜> variants) from user-facing assistant text, preventing GLM-5 and DeepSeek internal delimiters from reaching end users.

Check Agents/text sanitization 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.

The limits of the recovery promise

iOS/gateway foreground recovery

reconnect immediately on foreground return after stale background sockets are torn down, so the app no longer stays disconnected until a later wake path happens.

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

Run the smallest useful rehearsal

1. Write down the baseline for OpenRouter/models, including the installed version, host, provider, and workspace.
2. Confirm what can be restored, then take a verified backup before applying the candidate package.
3. Use a disposable session to compare the new model or provider with the previous route on one fixed input.
4. Restore the previous provider setting after the check and retain the measured result beside the release tag.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw models

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/text sanitization. strip leaked model control tokens (<|...|> and full-width <｜...｜> variants) from user-facing assistant text, preventing GLM-5 and DeepSeek internal delimiters from reaching end users. This is the edge case to include in a regression check, especially when the release is pre-release.

iOS/gateway foreground recovery. reconnect immediately on foreground return after stale background sockets are torn down, so the app no longer stays disconnected until a later wake path happens. Treat the fix as a boundary condition and retain the source wording beside your local result.

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