Summary In a direct chat with a bot, if the bot is actively showing a generated draft / streaming preview via sendMessageDraft, Telegram Android temporarily blocks the user from sending their own message in that chat. The normal send button is replaced by a green circular ellipsis/loading button, which makes the composer effectively unusable until the bot finishes generating.
Actual behavior
The send button is replaced by an ellipsis/loading button. While the bot-generated draft is active, the user cannot send a normal message or command in the same chat.
Expected behavior The user composer should remain usable at all times. The user should be able to send normal messages and bot commands while a bot-generated draft / preview is active. Bot draft/preview UI should not block user input.
Why this matters This is especially problematic in AI/bot chats, where users often need to interrupt, steer, correct, or stop the bot while it is still generating. If the composer is blocked during generation, commands like /steer, /stop, or simple correction messages cannot be sent in real time, which breaks the interaction model and creates a poor UX.
Steps to reproduce
Steps to reproduce
Open a direct chat with a bot that streams progress using sendMessageDraft.
Trigger a long-running bot action so the bot starts showing a generated draft / streaming preview.
While the bot is still generating, try to type and send a normal message or a bot command such as /steer please stop.