releaseadvanced
[Release] openclaw/openclaw v2026.4.19-beta.1: openclaw 2026.4.19-beta.1
By steipetegithub
View original on githubOpenClaw v2026.4.19-beta.1 releases critical fixes addressing cross-agent channel routing, Telegram callback handling, browser CDP connectivity, and Codex token accounting. Key improvements include proper account preservation in multi-agent setups, prevention of stale pagination buttons blocking updates, WSL-to-Windows Chrome endpoint detection, and accurate context usage reporting. Enhanced diagnostics for Windows browser startup failures provide better troubleshooting visibility.
Key Points
- •Cross-agent subagent spawns now route through target agent's bound channel account, preserving peer and workspace/role-scoped bindings while preventing child sessions from inheriting caller's account in shared environments
- •Permanent Telegram callback edit errors are treated as completed updates, preventing stale command pagination buttons from blocking the update watermark and newer incoming updates
- •Remote CDP profile host selection for health/control checks no longer widens browser navigation SSRF policy, enabling WSL-to-Windows Chrome endpoints to appear online under strict security defaults
- •Cumulative app-server token totals in Codex are no longer treated as fresh context usage, eliminating inflated context percentage reporting in long-running threads
- •Phase-specific CDP readiness diagnostics and loopback WebSocket host alias normalization provide granular Windows browser startup failure visibility (HTTP discovery, WebSocket discovery, SSRF validation, Browser.getVersion checks)
- •Multi-account setup stability improved through proper channel account routing in cross-agent scenarios
- •Browser connectivity diagnostics enhanced to distinguish between different failure modes in Windows environments
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