OpenClaw v2026.6.1-beta.1: Resilient agent and Codex runs, provider notes

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

Because this is a pre-release, use a disposable Gateway first and leave the stable version available for comparison. 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

Resilient agent and Codex runs

What changed. interrupted tool calls, stale session bindings, compaction handoffs, auth-profile failover, reasoning-tag cleanup, yielded subagents, and generated-media delivery all recover without leaving work stranded.

Check it with. Treat Resilient agent and Codex runs as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Reliable channel and mobile delivery

What changed. WhatsApp, iMessage, Discord state, QQBot, and iOS Talk now preserve replies, typing, session state, QR-login recovery, and realtime connections across normal restart and transport failure paths.

Check it with. Reliable channel and mobile delivery 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.

Faster Control UI chat

What changed. startup, local drafts, incremental stream rendering, transcript caching, first connect, and post-send cleanup no longer compete with the active conversation.

Check it with. Test Faster Control UI chat 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.

Governed skills and plugins

What changed. Skill Workshop proposals, disabled-skill snapshots, support-file approvals, plugin contracts, and external package boundaries are clearer and safer for operators.

Check it with. Treat Governed skills and plugins as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

What changes outside the chat box

Richer operator coordination

Workboard goals, task-backed runs, and SQLite-backed plugin state make multi-agent work and installed-plugin discovery survive reloads cleanly.

Keep Richer operator coordination inside a test workspace until you can inspect its ledger, next run, failure state, and cancellation behavior from the operator surface.

Skills

let the skill_workshop agent tool apply, reject, and quarantine explicit proposals through the guarded review flow.

Keep Skills inside a test workspace until you can inspect its ledger, next run, failure state, and cancellation behavior from the operator surface.

Skills

let proposals carry approved support files under standard skill folders, with scanner, hash, and rollback safeguards.

Keep discovery separate from permission for Skills. Review the manifest, source, dependencies, and removal path in a disposable workspace before enabling it.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Resilient agent and Codex runs.
2. Check the release's migration notes and make a restorable backup before changing persistent state.
3. Use a disposable conversation for one send, one reconnect, and one retry; keep the destination identifiers with the result.
4. Leave the channel disabled after the test if its credentials or pairing were created only for this rehearsal.
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

Build. render independent CLI startup metadata help snapshots concurrently to cut cold build-all metadata time. Record the failure that this correction addresses before declaring the upgrade complete.

Plugins. stop timed-out package-boundary prep steps by process group so descendant TypeScript/helper processes do not survive local check cleanup. This is the edge case to include in a regression check, especially when the release is pre-release.

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