releaseintermediate
[Release] openclaw/openclaw v2026.6.7-beta.1: openclaw 2026.6.7-beta.1
By vincentkocgithub
View original on githubOpenClaw v2026.6.7-beta.1 delivers significant improvements across channel delivery, provider resilience, security boundaries, and recovery paths. Key enhancements include tighter Slack/Telegram integration, better model handling for Kimi/Mistral/DeepSeek/Anthropic, safer auth contexts, and improved failure recovery for agents and cron jobs. The release also strengthens UI/docs accessibility, Docker bundling, and QA validation with new scorecard taxonomy artifacts.
Key Points
- •Channel delivery improvements: Slack transcript persistence, Telegram blockquote expansion, silent assistant replies, progress draft error reporting, and incremental paged action result fetching
- •Provider resilience: Added Kimi K2.7 Code support, fixed tool-call IDs and reasoning content replay, improved Mistral schema handling, and corrected Anthropic thinking replay
- •Security hardening: Feishu prompt-preface context isolation, WebSocket payload hardening, CLI fallback fail-closed behavior, and Skill Workshop symlink validation before rollback
- •Agent/memory recovery: Invalid plugin catalogs isolated, Codex memory prompts preserved, source message tool replies no longer block progress, structured error classification, and cron state preservation
- •UI/accessibility improvements: Contrast/focus/font fixes, collapsible Workboard columns, design-system documentation, and uptime monitor endpoints
- •QA and release validation: New scorecard taxonomy and evidence artifacts, trusted npm publishing for plugins, version alignment across packages, and Docker QA Lab bundling
- •Documentation expansion: Gateway uptime monitoring, design-system guidance, Windows Hub stable installer pins, WhatsApp compatibility, and doctor/update progress behavior
- •Failure recovery paths: Progress draft startup failures reported, heartbeat/cron terminal states preserved, Linux service updates handled cleanly, and SQLite store path reporting
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