[Release] openclaw/openclaw v2026.6.9: openclaw 2026.6.9

OpenClaw v2026.6.9 is a major release featuring enhanced Telegram delivery with rich HTML and markdown support, improved agent recovery through better retry and session history handling, stronger Codex integration with automatic plugin approvals and OAuth routing, standalone official provider plugins as npm packages, and more capable web and native clients with new UI features. The release includes 422 merged PRs addressing security, runtime stability, channel reliability, storage optimization, and operational improvements across the platform.

Key Points

• •Telegram now supports rich HTML delivery, preserves markdown formatting, renders progress drafts faithfully, normalizes HTML tables safely, and maintains proper mention and handler routing
• •Agent recovery improved through enhanced retries, terminal outcome handling, session history repair, and reply reconciliation to keep interrupted turns progressing toward visible results
• •Codex integration strengthened with automatic plugin approvals, GPT-5.3 Spark OAuth routing, remote-node exec as dynamic tool, and more reliable app-server teardown
• •Official provider plugins now published as independent npm packages with external installation at Gateway startup; StepFun available from npm and ClawHub
• •Web UI adds session workspace rail and extension health monitoring; iOS adds Watch controls; Android shows chat context for improved client experience
• •Codex Hosted Search now available; key-free search providers remain deliberate opt-ins; ClawHub skill installs retain verified source provenance
• •Security hardened through secret redaction from debug output, blocked internal HTTP session overrides, audited open-DM tool exposure, and retained plugin write ownership checks
• •Storage and migrations improved with SQLite WAL avoidance on network filesystems, clean reindex artifacts, proper setup state management, and auth profile imports
• •CLI/TUI enhancements include global flags after subcommands, visible terminal output, CJK IME composition preservation, and stale UI state refresh
• •QA and release engineering now use YAML scenarios with broader profile evidence and comprehensive plugin/channel matrix coverage

Workflow Diagram

Concepts