OpenClaw v2026.6.8-beta.2: More reliable agent runs, provider notes

v2026.6.8-beta.2 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

What changes outside the chat box

Predictable web search defaults

key-free providers such as Parallel Free, DuckDuckGo, Ollama, and Codex Hosted Search remain explicit opt-ins rather than surprising automatic fallbacks.

The safe reading of Predictable web search defaults is operational: prove the model can answer the intended task, then force a bounded failure and verify that no side effect is repeated.

Providers/models

add GLM-5.2 support and Claude Haiku 4.5 catalog entries while keeping provider-qualified model IDs normalized across OpenRouter and Google Vertex paths.

Check Providers/models with a known prompt and a disposable account. Save the selected route, reasoning setting, latency, and refusal or fallback result so another operator can reproduce it.

Web search

keep key-free providers such as Parallel Free, DuckDuckGo, Ollama, and Codex Hosted Search as explicit opt-ins instead of selecting them automatically when no API-backed provider is configured.

A catalog label for Web search is only the first signal. Confirm the account, endpoint, context limit, and tool policy that the running Gateway actually selected.

A bounded check for this version

1. Start with a disposable checkpoint: record the version, host, provider, and workspace tied to Richer channel delivery.
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

Channels and delivery. preserve account-scoped DM channel send policy, intentional rich-message line breaks in Telegram and status output, rich Telegram final replies, rich Telegram tables and lists, Telegram thread-create CLI remapping, Feishu dynamic-agent routes after persisted binding reuse, Slack outbound message_sent hooks, contributed message-tool schema optionality, same-channel generated media completions, and channel chunking around surrogate pairs and Infinity limits. Record the failure that this correction addresses before declaring the upgrade complete.

Gemini CLI. use the selected OpenClaw OAuth/API-key auth profile in an isolated Gemini CLI runtime home, preventing ambient Google machine credentials from overriding the chosen profile. 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.8-beta.2 GitHub release. The release index gives the surrounding sequence, while the model provider reference supplies the operational background.