releaseintermediate
[Release] openclaw/openclaw v2026.6.5-beta.2: openclaw 2026.6.5-beta.2
By github-actions[bot]github
View original on githubOpenClaw v2026.6.5-beta.2 introduces critical fixes for model reasoning leakage, MCP tool result handling, Anthropic extended-thinking recovery, and adds Parallel as a bundled web-search provider. The release improves durability of auth/plugin state via SQLite, enhances Matrix voice/thread support, and strengthens upgrade/service paths with safer migration and configuration handling. Multiple provider integrations (Google Vertex, WhatsApp, Mattermost) receive reliability improvements alongside comprehensive test isolation and CI/E2E enhancements.
Key Points
- •QQBot strips model reasoning/thinking scaffolding before delivery to prevent raw `<thinking>` content leakage into channel replies
- •MCP tool results now coerce non-text/image blocks (resource_link, audio, malformed images) at materialize boundary to prevent Anthropic 400s and poisoned session history
- •Anthropic extended-thinking sessions recover after prompt-cache expiry or Gateway restart by waiting for `message_start` stream events before triggering recovery retry
- •Parallel integrated as bundled `web_search` provider with `PARALLEL_API_KEY` discovery, guarded endpoint handling, cache-safe session IDs, and onboarding support
- •Auth profiles and npm plugin install records now persist in SQLite with trusted pins, improving durability across service restarts
- •Matrix channels support voice-message preflight and thread-aware read/reply behavior with full QA coverage for voice and thread flows
- •Google Vertex ADC users get static catalog rows, runtime model resolution, and more reliable single-provider cooldown recovery
- •macOS node mode no longer silently self-reconnects away from healthy direct Gateway sessions, reducing companion app session churn
- •Cron legacy JSON stores migrate during doctor preflight; service env placeholders no longer mask state-dir secrets; WhatsApp startup waits are bounded
- •Release numbering switched to `YYYY.M.PATCH` monthly patch format with June 2026 floor at `2026.6.5`; comprehensive test isolation reduces cross-test leakage
Found this useful? Add it to a playbook for a step-by-step implementation guide.
Workflow Diagram
Start Process
Step A
Step B
Step C
Complete