v2026.6.10

Automatic fast mode starts short conversations quickly, then returns longer or fallback work to normal mode without losing visible state. Provider routing, channel progress, session identity, and trusted tool policies are more reliable, with smaller improvements spanning provider setup, diagnostics, and transcript tooling.

Highlights

#### Automatic fast mode

• Adds `/fast auto` so short conversational calls can start quickly, while longer or fallback work returns to normal mode with the effective state still visible. PR #85104, Issue #85087. Thanks @alexph-dev and @vincentkoc.
• Shows the effective automatic fast-mode state in status instead of reducing it to on/off, and avoids carrying a cleared Codex service-tier choice into later runs. 8845f2f. Thanks @vincentkoc.
• Keeps automatic fast-mode timing consistent when a turn switches to a fallback model. 075091d. Thanks @vincentkoc.
• Keeps the original fast-mode timing and progress behavior when a live model switch retries a turn. d1e190f. Thanks @vincentkoc.
• Keeps automatic fast-mode progress and reset behavior distinct from explicit fast mode after a run switches modes. 20aec98. Thanks @vincentkoc.
• Shows the effective fast-mode value in connected-agent sessions instead of the configured value, so status reflects what the session is actually using. 9509aa0. Thanks @vincentkoc.
• Keeps the effective automatic fast-mode setting visible through fallback transitions in connected-agent sessions. 7f5423c. Thanks @vincentkoc.
• Keeps automatic fast-mode timing and progress consistent when reply and scheduled-agent runs retry or switch models. 6c29f88. Thanks @vincentkoc.
• Keeps fast-mode cleanup and status consistent when a run switches between fallback models. c4694f8. Thanks @vincentkoc.
• Shows the automatic fast-mode reset only when fallback work is finished, so status messages match the end of the transition. f4d93c8. Thanks @vincentkoc.
• Shows reset and delivery progress at the right time when auto-reply or other follow-up runs retry or leave automatic fast mode. 684e440. Thanks @vincentkoc.

Channels and Messaging

#### Channel delivery and progress updates

• Prevents the next turn after a scheduled message from losing what was delivered or whether delivery failed, so replies can use that context without exposing cron details in the channel. PR #93580. Thanks @jalehman and @scotthuang.
• Prevents streamed channel progress from dropping a repeated status that represents a separate step, so each meaningful step remains visible in the draft. 2d42e52. Thanks @vincentkoc.
• Prevents keyed streamed progress from staying on an older status, so viewers see the latest state instead of stale text. 8bb6472. Thanks @vincentkoc.

Providers and Models

#### Provider model catalogs and reasoning controls

• Treats Zhipu/GLM overload responses as overloads, so a configured fallback is selected for the right reason instead of following the wrong failover path. PR #93241, Issue #93211. Thanks @0xghost42 and @zhengli0922.
• Prevents Telegram, Slack, and Discord /think menus for live Ollama models from hiding supported levels, so users can choose valid reasoning settings without guessing. PR #94067, Issue #93835. Thanks @civiltox and @openperf.
• Expands `zai/glm-5.2` thinking choices beyond binary on/off and sends high or max requests as the intended Z.AI reasoning effort. PR #94136. Thanks @borclaw.
• Prevents bundled Z.ai GLM-5 models from falling through to OpenAI and producing misleading API-key errors, so they use Z.AI by default. PR #94461, Issue #94269. Thanks @chrysb and @pandah97.
• Adds GLM-5.2 and Kimi K2.7 Code to the OpenCode Go catalog with current limits, so users can select the models from OpenClaw. 66f84a9. Thanks @samson1357924.
• Corrects kimi-k2.7-code capability listings so OpenCode Go users are not offered unsupported video prompts when the model accepts text and images. 715dc71.

#### Provider plugin onboarding

• Prevents first-run setup from skipping the selected provider's credential prompt after plugin installation, so onboarding continues with that provider instead of falling back to OpenAI. PR #95792, Issue #95765. Thanks @snowzlmbot.

Memory, Sessions, and State

#### Session transcript SDK helpers

• Adds a durable session-transcript SDK contract so plugins can read, append, publish, and lock the intended transcript without treating legacy file paths as identity. PR #95030. Thanks @jalehman.

#### Cross-channel session identity

• Prevents a shared direct-message session from carrying the previous channel's identity after a switch, so status, reactions, threads, and message references target the current channel. PR #95328, Issue #95325. Thanks @gorkem2020, @jalehman, and @zengwen-dt.

Gateway, Security, and Trust

#### Prompt context boundaries

• Keeps empty prompts separate from hook-added context during compaction or session reuse in Copilot and Codex sessions, so prompt boundaries remain consistent. PR #94838. Thanks @vincentkoc.

#### Trusted tool policy enforcement

• Keeps approval-sensitive Gateway and plugin tools protected when connected extensions change, so configured safeguards continue to apply. PR #94545. Thanks @jesse-merhi.

#### Trusted package redirects

• Prevents authenticated package-source tokens from being sent to an allowed redirect on another origin, while the valid redirected download still completes. b0df6dc.

Clients and Interfaces

#### Docker and Podman setup timeouts

• Prevents Docker and Podman setup from running unbounded on hosts where GNU timeout is installed as gtimeout, so image pulls, builds, and detached startup receive the intended guard. 62b2e9e.

Plugins and Packaging

#### Codex service-tier clearing

• Prevents cleared Codex service tiers from being persisted as explicit stale state, so resumed or switched conversations use the normal default instead. cd32d9f. Thanks @vincentkoc.

#### StepFun provider installation

• Restores ClawHub discovery for the StepFun provider plugin, so operators can install it through either ClawHub or npm. ecb82f1. Thanks @vincentkoc.

Docs and Operator Workflows

#### Doctor check ordering

• Keeps core `openclaw doctor` diagnostics in their normal order before extension checks, making lint and repair output easier to follow. PR #86627. Thanks @giodl73-repo.

Release verification

• npm package: https://www.npmjs.com/package/openclaw/v/2026.6.10
• registry tarball: https://registry.npmjs.org/openclaw/-/openclaw-2026.6.10.tgz
• integrity: sha512-LcooND2tBQw8A+kc1Ujltu3lg30bJ0w7XaeRy7eYzobb8BBdcW6DOGbwJL4vpj1vl9+gjRceOtlh5nh9OARcug==
• release SHA: aa69b12d0086b631b139c1435c9621a5783e3a40
• full release CI report: https://github.com/openclaw/releases/blob/main/evidence/2026.6.10/release-evidence.md
• release publish: https://github.com/openclaw/openclaw/actions/runs/28071368306
• npm preflight: https://github.com/openclaw/openclaw/actions/runs/28068484614
• full release validation: https://github.com/openclaw/openclaw/actions/runs/28068476120
• plugin npm publish: https://github.com/openclaw/openclaw/actions/runs/28071564667
• plugin ClawHub publish: https://github.com/openclaw/openclaw/actions/runs/28071565774
• plugin ClawHub bootstrap: not needed
• OpenClaw npm publish: https://github.com/openclaw/openclaw/actions/runs/28071984141
• npm Telegram beta E2E: not supplied
• Windows Hub promotion: https://github.com/openclaw/openclaw/actions/runs/28072271374 from openclaw/openclaw-windows-node@v0.6.3