What happened
Telegram’s Bot API changelog dates the release to November 9, 2026. Version 10.4 adds a Widget class and a widget field to Message and ExternalReplyInfo for messages containing HTML widgets. Bots can send widget messages with the new sendWidget method. Telegram says that, in the production environment, widgets can currently be sent only to private chats. Sent widgets automatically have protected content and therefore cannot be forwarded.
The update adds methods for the interaction after a widget is delivered. sendSharedWidget lets a bot send again shared widgets that the bot created. The API adds WidgetQuery and SharedWidgetQuery update types for queries originating from widgets in messages sent by the bot or from forwarded messages containing shared widgets. Bots can respond to widget queries with answerWidgetQuery. They can also change data using editMessageWidgetData for a widget in a message, or editSharedWidgetData for public data associated with a shared widget.
The changelog also describes the shapes of widget queries. The new WidgetQueryType, WidgetQueryTypeData, WidgetQueryTypeSignData, WidgetQueryTypeSentTransaction and WidgetQueryWallet classes cover query types that can include data for the bot, a TON wallet card belonging to the user, data signed by a TON wallet, or a notification about a transaction sent from a TON wallet. These are API-level representations of the query and its associated information; the changelog does not describe a particular application built on them.
For inline-query workflows, Telegram adds InputWidgetMessageContent and InputSharedWidgetMessageContent, allowing bots to send widgets in response to inline queries. But the changelog explicitly says widgets cannot currently be sent in response to inline queries in production. It also says widget messages cannot be copied with copyMessage or copyMessages. Finally, Telegram expands the meaning of the can_send_other_messages right in ChatPermissions and ChatMemberRestricted: that permission now allows sending widgets as well.
What the archive adds
New Runtime’s earlier coverage includes Telegram’s open-source widget-sandbox (November 7, 2026), a tool for creating and testing HTML widgets embedded in messages, and OpenClaw’s Telegram widget support (November 12, 2026). Bot API 10.4 is a new platform-level event: it adds official methods and query types rather than describing another widget implementation.
Trend signal
This update supports agent-ready software exposes capabilities: Telegram is defining explicit methods and query types through which bots can deliver and interact with widgets. The API surface is concrete, but this is not evidence that widgets are broadly available across chat contexts: production sending is limited to private chats, and inline-query sending remains unavailable there.
Why now
The changelog dates Bot API 10.4 to November 9, 2026, after Telegram’s earlier additions of widget-related tooling and support covered by New Runtime. The API release provides a platform interface for sending and handling widgets, while its stated production restrictions set the current scope.
Connections to other events
New Runtime’s November 7, 2026 coverage of Telegram’s widget-sandbox concerned creating and testing HTML widgets embedded in messages. Its November 12, 2026 coverage of OpenClaw’s Telegram widget support concerned an implementation using Telegram widgets. Bot API 10.4 adds the official bot-facing interface for sending widgets and processing their queries; it does not establish that those projects use every new method.
Why it matters
For teams building Telegram bots, HTML widgets create a path to put interactive experiences directly in a conversation rather than relying only on ordinary message text and buttons. The new query and edit methods also make the interaction lifecycle part of the bot API: a bot can receive a widget-originated query, answer it and update widget data. That gives developers a clearer integration surface to design against.
The restrictions matter just as much as the new methods. A product intended to distribute widgets through groups, channels or inline results cannot assume those routes work in production. Automatic protection against forwarding also changes how a widget can spread between users. Teams should prototype within the private-chat constraint and confirm that their intended sharing and copying behavior does not depend on unsupported paths before committing to the experience.
Limits and uncertainty
Telegram’s changelog establishes the API additions and states several production restrictions, but it does not report adoption, reliability, latency or the performance of widget experiences. It does not describe how developers should host or secure widget content, nor does it quantify the audience or operational cost of the feature. The production support boundary could change; the release notes do not give a date for enabling inline-query responses or broader chat availability. The practical behavior of individual widget flows should be validated against the API and Telegram clients developers target.
Reader takeaway
Bot API 10.4 makes HTML widgets a first-class bot capability, with methods for sending, handling queries and updating data. Treat private chats as the current production boundary, and design around protected, non-forwardable messages; inline-query responses and message copying are not available for widgets in production.
Open question
When will Telegram enable widget sending in production beyond private chats and in response to inline queries?