OpenClaw: Stability Fixes and Platform Improvements

Transcript

Good morning. This is your OpenClaw developer briefing for May 18th, 2026.

The team merged 20 pull requests yesterday, led by significant stability improvements. 100yenadmin merged a comprehensive release stability recovery fix, hardening auth fallback systems and addressing stuck sessions that were queuing behind terminal-looking embedded progress. This targeted fix helps operators running unstable release paths while the mainline settles.

steipete contributed multiple messaging system fixes, including reverting group channel visible replies back to automatic delivery by default, and ensuring TTS directives apply before message-tool sends reach their destination. These changes address workflow interruptions in shared group rooms.

Platform integrations saw several key improvements. joshavant fixed a critical issue where Telegram images weren't reaching Ollama vision models in native PI runs, and recovered stalled Telegram isolated spool handlers that were causing message processing delays. sliverp shortened QQBot's typing keepalive window from 60 seconds to 10 seconds with 5-second renewals, improving responsiveness when users switch between conversations.

samzong optimized gateway startup performance by overlapping independent startup work before ready state, reducing restart latency without weakening readiness contracts. The team also added gateway restart benchmark tooling for measuring performance regressions.

Additional fixes included Codex sandbox egress preservation for app-server turns, childless Codex native subagent task recovery, and comprehensive linting improvements with no-underscore-dangle rules.

What's next: The team continues working on release stability hardening and expects further messaging system refinements. Performance optimization work on gateway operations remains ongoing.

That's your OpenClaw update. Back tomorrow with more developer news.