The source record for v2026.6.10 names a provider, model, voice, or context change. This is an operator's reading of that record, with the exact source facts kept next to a bounded experiment rather than a generic feature list.
Treat this as a stable maintenance checkpoint and keep the release record beside the backup and rollback evidence. A release tag describes the project change. Your Gateway's provider, channel, platform, and account support should be recorded separately.
Channel
Stable
Primary signals
Adds /fast auto so short conversational; Shows the effective automatic fast-mode; Keeps automatic fast-mode timing
Publication date
2026-06-24
A small field test
Adds /fast auto so short conversational calls can start
What changed. 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.
Check it with. A successful click does not establish Adds /fast auto so short conversational calls can start. Compare the state before and after a reload, then verify that a user can tell what happened without reading internal logs.
Shows the effective automatic fast-mode state in status
What changed. 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.
Check it with. A catalog label for Shows the effective automatic fast-mode state in status is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.
Keeps automatic fast-mode timing consistent when a turn
What changed. Keeps automatic fast-mode timing consistent when a turn switches to a fallback model. 075091d.
Check it with. The safe reading of Keeps automatic fast-mode timing consistent when a turn is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.
Keeps the original fast-mode timing and progress
What changed. Keeps the original fast-mode timing and progress behavior when a live model switch retries a turn. d1e190f.
Check it with. The safe reading of Keeps the original fast-mode timing and progress is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.
The details that affect a runbook
Keeps automatic fast-mode progress and reset behavior
Keeps automatic fast-mode progress and reset behavior distinct from explicit fast mode after a run switches modes. 20aec98.
Use Keeps automatic fast-mode progress and reset behavior for a small reproducible task: save the input, visible result, useful failure, and version context another operator would need.
Operator checklist before rollout
- Before touching persistent state, capture the version, host, provider, and workspace for Adds /fast auto so short conversational calls can start.
- Read the linked release record and verify a backup whenever the change can alter configuration or session data.
- Exercise the named capability with a non-sensitive prompt, including the fallback or refusal result if it occurs.
- Force a timeout or provider fallback in a disposable session and verify that no side effect is repeated.
- Close the test with the evidence attached, and do not widen the rollout while a behavior remains unexplained.
openclaw --version
openclaw gateway status
openclaw models
Keep the source trail attached
Close the loop with an explicit next action: keep the candidate isolated, proceed with the staged upgrade, or stop and investigate. Do not treat a green install as proof that the runtime path is correct.
This page is a practical reading of the v2026.6.10 source record; the release index and model provider reference remain the references to use for migrations and support boundaries.
Reference Trail
Sources and further reading
- v2026.6.10 source recordgithub.com
- release indexgithub.com
- model provider referencedocs.openclaw.ai