OpenClaw v2026.3.11: iOS/Home canvas, provider notes

v2026.3.11 changes how an agent selects, calls, or remembers a provider. The official record describes a provider, model, voice, or context change; the useful test is a small request with the provider boundary recorded.

This is a stable release line; read the exact record for migrations and fixes before applying it to a live Gateway. The release body cannot certify every local combination of provider, channel, platform, and account; use the bounded test below for the path you actually run.

Provider and model consequences

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.

A catalog label for OpenRouter/models is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

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.

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

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.

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

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.

A catalog label for Agents/text sanitization is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

What changes outside the chat box

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.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to OpenRouter/models.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Ask the same small question through the affected route and record the account, model id, context, and response time.
4. Compare the answer, tool permissions, and fallback behavior with the baseline before changing a default.
5. If the result differs from the release body, stop the rollout and attach the log, screenshot, or transcript to the version record.

openclaw --version
openclaw gateway status
openclaw models

Close the loop with evidence

A useful maintenance record names the changed behavior, the behavior that stayed stable, the identity that approved the test, and the step that would undo it. Preserve that record beside the release tag.

Edge cases in this tag

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. Record the failure that this correction addresses before declaring the upgrade complete.

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. This is the edge case to include in a regression check, especially when the release is pre-release.

The authoritative record is the v2026.3.11 GitHub release. The release index gives the surrounding sequence, while the model provider reference supplies the operational background.