OpenClaw v2026.6.1-beta.2: Reliable channel and mobile delivery, upgrade notes

v2026.6.1-beta.2 arrived on 2026-06-01 with a change that matters during maintenance: reliable channel and mobile delivery. The page is a researched reading note from the official release record, with a test path for a real Gateway.

The tag is pre-release: keep it isolated from a production Gateway and compare it with the stable line before making it a default. Support still depends on the provider, channel, platform, and account behind the installation, so check those boundaries before extrapolating from the tag.

Before the package changes

01 / Resilient agent and Codex runs

Source signal. 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.

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.

02 / Reliable channel and mobile delivery

Source signal. 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.

For Reliable channel and mobile delivery, 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.

03 / Faster Control UI chat

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

For Faster Control UI chat, 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 / Governed skills and plugins

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

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.

Details behind the headline

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.

Test this release without widening the boundary

1. Note the current version, host, provider, and workspace before exercising Resilient agent and Codex runs.
2. Keep a tested backup beside the release record if the update can touch configuration, sessions, or a database.
3. Send one harmless message through the named account and save the account, thread, and sender identifiers.
4. Compare the transcript before and after reconnect, including delivery state and any visible error.
5. Stop if the observed behavior falls outside the official note, and link the log or screenshot to the version record.

openclaw --version
openclaw gateway status
openclaw security audit

Record what the release actually changed

Keep the version, source URL, test identity, and rollback decision together. If this tag is pre-release, leave it isolated; if it is stable, record the migration and rollback result before reconnecting every channel.

Corrections worth replaying

Build. render independent CLI startup metadata help snapshots concurrently to cut cold build-all metadata time. Keep the reproduction and the post-fix result together in the acceptance record.

Plugins. stop timed-out package-boundary prep steps by process group so descendant TypeScript/helper processes do not survive local check cleanup. Record the failure that this correction addresses before declaring the upgrade complete.

Use the complete OpenClaw v2026.6.1-beta.2 release notes for the exact change list, then cross-check the official release index and the model provider reference before acting.