releaseintermediate
[Release] openclaw/openclaw v2026.6.5-beta.3: OpenClaw 2026.6.5-beta.3
By vincentkocgithub
View original on githubOpenClaw v2026.6.5-beta.3 introduces critical fixes for model reasoning leakage in QQBot, MCP tool result coercion to prevent API errors, improved Anthropic extended-thinking session recovery, and a new bundled Parallel web-search provider. The release strengthens security around tool access, improves provider/model resolution reliability, and enhances durability of auth and plugin state through SQLite persistence. Multiple platform-specific improvements address macOS node reconnection issues, Matrix voice/thread handling, and mobile UI clarity.
Key Points
- •QQBot now strips model reasoning/thinking scaffolding before delivery to prevent raw `<thinking>` content from leaking into channel replies
- •MCP tool results are coerced at the materialize boundary to handle `resource_link`, `resource`, `audio`, and malformed image blocks, preventing Anthropic 400s and poisoned session history
- •Anthropic extended-thinking sessions recover after prompt-cache expiry or Gateway restart by waiting for `message_start` events before stream start
- •Parallel is now a bundled `web_search` provider with `PARALLEL_API_KEY` discovery, guarded endpoint handling, and cache-safe session IDs
- •Auth profiles now live in SQLite for durability; official npm plugin install records maintain trusted pins with prerelease fallback integrity checks
- •Agent, tool, and provider loops enforce stricter MCP lease timestamp validation, prompt-cache tool name guarding, and owner-only HTTP tool access controls
- •macOS node mode no longer silently self-reconnects away from healthy direct Gateway sessions, reducing unexpected companion app session churn
- •Google Vertex ADC users get static catalog rows and runtime model resolution with improved single-provider cooldown recovery and memory adapter status checks
- •Matrix channels now support voice-message preflight and thread-aware read/reply behavior with QA coverage for voice and thread flows
- •Release numbering switched to `YYYY.M.PATCH` monthly patch format with June 2026 floor at `2026.6.5`
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