OpenClaw v2026.6.9: Standalone official provider plugins, recovery notes

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

The limits of the recovery promise

More capable web and native clients

the Control UI adds a session workspace rail and extension health, iOS adds Watch controls, and Android shows chat context.

For More capable web and native clients, 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.

Providers and auth

add Codex Hosted Search, improve Gemini CLI OAuth behind proxies, and keep external provider onboarding on current choices and package metadata.

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

Plugins and installs

externalized official providers publish as independent npm packages, Gateway discovers installed channel plugins at startup, and StepFun installs from npm or ClawHub.

Plugins and installs 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.

Run the smallest useful rehearsal

1. Write down the baseline for Richer Telegram delivery, 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

Security and privacy. redact secrets from debug/config output, block internal HTTP session overrides, audit open-DM tool exposure, and retain plugin write ownership checks. This is the edge case to include in a regression check, especially when the release is pre-release.

Agent and session runtime. retry thinking-only and empty post-tool turns, prevent duplicate hook execution, preserve pending subagent delivery, preserve fresh usage through compaction, and repair partial JSON/history artifacts. Treat the fix as a boundary condition and retain the source wording beside your local result.

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