OpenClaw v2026.4.14-beta.1 was published on 2026-04-14T02:07:43Z by steipete. OpenClaw v2026.4.14-beta.1 improves Telegram topic context, hardens the Control UI against markdown-based freezes, and fixes send-policy behavior in observer-style setups.
Quick answer
The strongest themes here are safer UI rendering, better Telegram context, and fewer unexpected behavior changes when teams suppress outbound sending but still expect the agent to process inbound turns.
What's new in this release
- Telegram/forum topics: surface human topic names in agent context, prompt metadata, and plugin hook metadata by learning names from Telegram forum service messages. (#65973) Thanks @ptahdunbar.
- UI/chat: replace marked.js with markdown-it so maliciously crafted markdown can no longer freeze the Control UI via ReDoS. (#46707) Thanks @zhangfnf.
- Auto-reply/send policy: keep `sendPolicy: "deny"` from blocking inbound message processing, so the agent still runs its turn while all outbound delivery is suppressed for observer-style setups. (#65461, #53328) Thanks @omarshahine.
- BlueBubbles: lazy-refresh the Private API server-info cache on send when reply threading or message effects are requested but status is unknown, so sends no longer silently degrade to plain messages when the 10-minute cache expires. (#65447, #43764) Thanks @omarshahine.
- Heartbeat/security: force owner downgrade for untrusted `hook:wake` system events [AI-assisted]. (#66031) Thanks @pgondhi987.
Why developers should care
This beta is most relevant for Telegram-heavy setups, Control UI users, and maintainers validating policy or security-sensitive chat surfaces.
Upgrade notes
No explicit breaking changes were called out in the fetched GitHub release notes. Even so, teams using custom providers, plugins, or channel integrations should review the full release notes before rolling forward.
Source
Full release notes: https://github.com/openclaw/openclaw/releases/tag/v2026.4.14-beta.1