OpenClaw v2026.3.1: Android/Nodes, provider notes

v2026.3.1 changes how an agent selects, calls, or remembers a provider. The official record describes a health, liveness, or runtime-observability 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

Agents/Thinking defaults

What changed. set adaptive as the default thinking level for Anthropic Claude 4.6 models (including Bedrock Claude 4.6 refs) while keeping other reasoning-capable models at low unless explicitly configured.

Check it with. Agents/Thinking defaults changes a capability choice, not automatically a billing or privacy agreement. Record provider, model id, context setting, and fallback behavior before changing a default.

Gateway/Container probes

What changed. add built-in HTTP liveness/readiness endpoints (/health, /healthz, /ready, /readyz) for Docker/Kubernetes health checks, with fallback routing so existing handlers on those paths are not shadowed.

Check it with. For Gateway/Container probes, delivery is only proven when identity survives an interruption. Keep a disposable channel, send one request, and check for a single reply in the intended thread.

Android/Nodes

What changed. add camera.list, device.permissions, device.health, and notifications.actions (open/dismiss/reply) on Android nodes, plus first-class node-tool actions for the new device/notification commands.

Check it with. Read Android/Nodes as an authorization checkpoint: prove who may act, what the action can reach, and how the rejected attempt is surfaced to the operator.

Android/Nodes reliability

What changed. reject facing=both when deviceId is set to avoid mislabeled duplicate captures, allow notification open/reply on non-clearable entries while still gating dismiss, trigger listener rebind before notification actions, and scale invoke-result ack timeout to invoke budget for large clip payloads.

Check it with. The visible promise in Android/Nodes reliability needs a continuity check. Use non-sensitive data, refresh midway, and confirm that the same work remains attached to the right session.

What changes outside the chat box

Windows/Plugin install

avoid spawn EINVAL on Windows npm/npx invocations by resolving to node + npm CLI scripts instead of spawning .cmd directly. Landed from contributor PR #31147 by @codertony.

The maintainer check for Windows/Plugin install is a complete package review: identify the entry point, requested access, dependency tree, and uninstall behavior before publishing or upgrading.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Agents/Thinking defaults.
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 security audit

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

Android/Nodes reliability. reject facing=both when deviceId is set to avoid mislabeled duplicate captures, allow notification open/reply on non-clearable entries while still gating dismiss, trigger listener rebind before notification actions, and scale invoke-result ack timeout to invoke budget for large clip payloads. Record the failure that this correction addresses before declaring the upgrade complete.

Windows/Plugin install. avoid spawn EINVAL on Windows npm/npx invocations by resolving to node + npm CLI scripts instead of spawning .cmd directly. Landed from contributor PR #31147 by @codertony. 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.1 GitHub release. The release index gives the surrounding sequence, while the Gateway health guide supplies the operational background.