Add native DM draft previews for Telegram tool progress
TL;DR
Telegram integration now supports allowlisted native DM draft previews for transient tool progress while keeping final answers on the normal persistent delivery path.
What changed
OpenClaw added native DM draft previews to its Telegram integration on May 21, 2026. The update lets allowlisted chats show transient tool progress inside draft messages while final answers stay on the normal persistent path.
This keeps progress updates from creating extra chat history entries. The feature requires explicit allowlisting of specific DMs in the configuration file.
Why it matters
The change cuts down on notification spam during long-running tasks such as browser sessions or shell commands. Vibe Builders who rely on Telegram for daily agent contact gain a cleaner view of what the agent is doing without constant new messages.
It strengthens OpenClaw's position against closed agents that offer real-time status in their own interfaces. The bet is that better async polish in existing chat apps will keep users from switching to managed cloud tools.
How to use it
Update OpenClaw to the current release through the CLI and edit the YAML file to add Telegram chat IDs under the new draft_preview_allowlist key. Restart the agent and trigger a multi-step tool call from an allowlisted DM to see the drafts appear.
No extra plan or payment is required since the agent remains free and self-hosted. The feature works on any connected LLM provider once the config change is saved.
Watch for
Track whether draft previews reduce total Telegram messages by a noticeable amount in the next month of use. The approach fails if Telegram restricts draft access or if progress leaks appear in shared chats.
The next logical step is similar draft support for Discord and WhatsApp integrations.
Who this matters for
- Vibe Builders: Enable the draft_preview_allowlist in your YAML to see live agent progress without notification spam.
- Developers: Implement the new Telegram draft preview logic to handle transient tool states without bloating chat history.
Harsh’s take
OpenClaw is solving the biggest friction point in chat based agents: the notification flood. By hijacking the Telegram draft state for transient tool progress, they provide a real time UI feel within a standard messaging app. This is a clever technical workaround that keeps users in their existing workflows rather than forcing them into a custom dashboard.
Operators should view this as a blueprint for async agent design. It prioritizes a clean chat history while maintaining transparency during long running browser or shell tasks. The requirement for explicit allowlisting suggests this is still a power user feature, but it significantly raises the bar for self hosted agent polish.
If you are building Telegram bots, this draft preview pattern is the new standard for UX.
by Harsh Desai
About OpenClaw
View the full OpenClaw page →All OpenClaw updatesMore from OpenClaw
- App UpdateAdd doctor warnings for hidden MCP server tools
The doctor utility now warns users when sandbox tool policies hide configured Model Context Protocol (MCP) server tools before provider requests are made.
- App UpdateExpose stale-running task maintenance details in CLI
The tasks maintenance CLI command now outputs detailed JSON explanations for retained and reconcile candidates, detailing backing-session, cron, CLI, and wedged-subagent states.
- FeatureSupport per-agent lean local-model configuration
Added support for the experimental localModelLean configuration option on individual agents. This allows lean local-model mode to be enabled selectively rather than globally.