Description
When an agent produces multiple replies in a single turn, the Telegram channel is expected to deliver them as separate, sequential messages when blockStreaming: true and streamMode: "off" are configured. However, the actual behavior is that all messages except for the very last one are dropped and never delivered to Telegram. They are visible in the OpenClaw dashboard logs, but they do not reach the client.
Steps to Reproduce
- Configure
openclaw.json with the following settings for the Telegram channel:
"telegram": {
"streamMode": "off",
"blockStreaming": true
}
- Restart the OpenClaw gateway.
- In a single agent turn, have the agent send a message, then call a tool, then send a second message.
Expected Result
The user in Telegram receives both the first and second messages sequentially.
Actual Result
The user in Telegram receives only the second message. The first message is never delivered.
System Information
- OpenClaw Version: 2026.2.12
- Platform: macOS Darwin 22.6.0
- Node.js Version: v24.13.0
Description
When an agent produces multiple replies in a single turn, the Telegram channel is expected to deliver them as separate, sequential messages when
blockStreaming: trueandstreamMode: "off"are configured. However, the actual behavior is that all messages except for the very last one are dropped and never delivered to Telegram. They are visible in the OpenClaw dashboard logs, but they do not reach the client.Steps to Reproduce
openclaw.jsonwith the following settings for the Telegram channel:Expected Result
The user in Telegram receives both the first and second messages sequentially.
Actual Result
The user in Telegram receives only the second message. The first message is never delivered.
System Information