OpenClaw v2026.6.1: Resilient agent and Codex runs, recovery notes

v2026.6.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.

Stable status describes the release line, not every local provider or channel. Check the version-specific notes before upgrading. 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

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. Before widening access for Resilient agent and Codex runs, replay a narrow allow and deny case. A readable denial and a revoked test credential are part of the acceptance record.

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. The operator question around Reliable channel and mobile delivery is where the reply lands after a restart. Record the conversation identifiers before testing and compare them after the channel is healthy again.

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. A successful click does not establish Faster Control UI chat. Compare the state before and after a reload, then verify that a user can tell what happened without reading internal logs.

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. The useful evidence for Governed skills and plugins is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

The limits of the recovery promise

Richer operator coordination

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

For Richer operator coordination, write down the owner and retry boundary before running anything. Repeat the trigger and check that recovery does not create a second message, job, or file.

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.

Use Skills to test ownership as well as installation. Confirm which agent owns the skill or plugin and that a missing or rejected package cannot mutate another workspace.

Run the smallest useful rehearsal

1. Write down the baseline for Resilient agent and Codex runs, 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. Exercise the affected channel with synthetic text and note the thread, sender, reaction, or attachment id that comes back.
4. Restart or reconnect the Gateway, then check for one intended reply rather than a duplicate, missing, or misrouted message.
5. Keep the experiment bounded; an unexpected result belongs in the release record before any wider rollout.

openclaw --version
openclaw gateway status
openclaw security audit

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

Build. render independent CLI startup metadata help snapshots concurrently to cut cold build-all metadata time. This is the edge case to include in a regression check, especially when the release is pre-release.

Plugins. stop timed-out package-boundary prep steps by process group so descendant TypeScript/helper processes do not survive local check cleanup. Treat the fix as a boundary condition and retain the source wording beside your local result.

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