releaseintermediate
[Release] openclaw/openclaw v2026.5.31-beta.2: openclaw 2026.5.31-beta.2
By steipetegithub
View original on githubOpenClaw v2026.5.31-beta.2 introduces significant stability improvements for agent runtimes, channel delivery, and plugin management. Key enhancements include better recovery from interrupted tool calls, steadier multi-channel support (Telegram, WhatsApp, Slack, Discord, Teams, etc.), bounded timers and retries to prevent hangs, and new Skill Workshop orchestration features. The release also externalizes Tokenjuice and GitHub Copilot as official plugins, adds iOS push relay improvements, and strengthens CI/E2E testing with comprehensive logging caps and artifact validation.
Key Points
- •Agents and CLI runtimes now recover cleanly from interrupted tool calls, stale sessions, compaction handoffs, and media retries (#88129, #88136, #88141, #88162, #88182)
- •Multi-channel delivery stabilized across 9+ platforms (Telegram, WhatsApp, iMessage, Slack, Discord, Teams, Google Chat/Meet, iOS) with improved WebSocket and realtime Talk support
- •Provider and plugin requests now have bounded timers, retries, OAuth lifetimes, media downloads, and polling paths to prevent run hangs
- •Skill Workshop feature enables governed skill creation with CLI/Gateway review, proposal versioning, approval workflows, and rollback safeguards
- •Tokenjuice and GitHub Copilot externalized as official npm/ClawHub plugins (@openclaw/tokenjuice, @openclaw/copilot)
- •iOS push relay defaults and guarded WebSocket ping paths improve mobile session reliability
- •Workboard adds multi-agent orchestration primitives and run tracking coordination tools
- •CI/E2E lanes now cap logs, response bodies, readiness probes, and artifact checks to prevent stalling and ensure bounded failure reporting
- •Security hardening: unsafe OAuth/token lifetimes, retry delays, response sizes, and command timeouts are now rejected during config parsing
- •Hot-path optimization: skills, session metadata, gateway state, and store writes reduced repeated work while maintaining stable config and dispatch behavior
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