OpenClaw v2026.6.10-beta.1: More reliable agent turns and session state, provider notes

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

01 / More reliable agent turns and session state

Source signal. OpenClaw now preserves pending subagent completion announcements, keeps chat history transcripts non-empty, maintains media index alignment, restarts dormant follow-up drains, and resolves compaction model aliases consistently.

A catalog label for More reliable agent turns and session state is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

02 / Stronger Codex and approval flows

Source signal. Codex app-server SecretRefs, thread context, bounded turn text, routed approval context, and typed SDK approval/session helpers now work together more predictably.

The useful evidence for Stronger Codex and approval flows is the refusal path as well as the success path. Use synthetic credentials and record the policy that made each decision.

03 / Richer channel delivery

Source signal. Telegram, Discord, and Slack now preserve richer progress/reasoning/thread output, handle structured send errors, support Slack shortcuts, and record canonical sent threads more reliably.

For Richer channel 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.

04 / Safer release and network boundaries

Source signal. SSH tunnel preflight is loopback-scoped, device-backed node pairings are removed, volatile SQLite state is surfaced by doctor, and legacy Codex routes are repaired instead of silently persisting stale state.

The safe reading of Safer release and network boundaries is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

What changes outside the chat box

Useful new CLI and status workflows

Rename sessions from chat, compact sessions explicitly, show session duration, preserve command progress detail, and preview message sends/polls with dry-run output.

Useful new CLI and status workflows 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.

Agent and provider behavior

Codex turn limits, CLI-owned auth, provider-internal error wording, recurring cron backoff, explicit cron delivery targets, and isolated cron key requirements now fail or recover more clearly.

Treat Agent and provider behavior as a boundary change. Exercise one permitted request and one refused request with a test identity, then keep both decisions in the log.

Channels and integrations

WhatsApp retries the opening text chunk after media failure, Feishu avoids axios internals, Slack records inbound mentions and preserves buffered streams, and external Zalo/Slack shortcuts are wired through the current channel seams.

For Channels and integrations, 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.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to More reliable agent turns and session state.
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

Reply and transcript correctness. OpenClaw now keeps pending completions, non-empty histories, media fields, queued follow-ups, buffered Slack replies, and reasoning deliveries intact across retries and partial turns. Record the failure that this correction addresses before declaring the upgrade complete.

Security and bounded input handling. SSH tunnel checks stay on loopback, unsafe chat/tool/package/response lengths are rejected, device-backed pairings are removed, and stale abort markers no longer affect fresh chat events. 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.10-beta.1 GitHub release. The release index gives the surrounding sequence, while the model provider reference supplies the operational background.