Problem
Some messages from the agent are not delivered to Telegram when:
- A Heartbeat arrives
- A User message is already queued/arrives at the same time
- The agent responds to both
The Heartbeat response appears to "overwrite" or cancel the normal reply.
Evidence
Screenshot showing missing message in chat:
- Agent sent a message about an upcoming workshop (visible in agent logs/session)
- Message never appeared in Telegram chat
- User confirmed: "da ist nichts" (nothing there)
Config
{
"channels": {
"telegram": {
"enabled": true,
"dmPolicy": "pairing",
"groupPolicy": "open",
"streamMode": "partial"
}
}
}
Hypothesis
The streamMode: "partial" may cause race conditions when multiple responses are being streamed/edited simultaneously. The in-place message editing could fail silently.
Expected Behavior
All agent messages should be reliably delivered, even when Heartbeats and user messages arrive close together.
Environment
- Clawdbot version: 2026.1.24-2
- OS: Linux 6.8.0-90-generic (arm64)
- Node: v22.21.0
- Telegram: DM with paired user
Workaround
Using the explicit message tool (action=send) appears to work reliably. Only "normal" replies seem affected.
Problem
Some messages from the agent are not delivered to Telegram when:
The Heartbeat response appears to "overwrite" or cancel the normal reply.
Evidence
Screenshot showing missing message in chat:
Config
{ "channels": { "telegram": { "enabled": true, "dmPolicy": "pairing", "groupPolicy": "open", "streamMode": "partial" } } }Hypothesis
The
streamMode: "partial"may cause race conditions when multiple responses are being streamed/edited simultaneously. The in-place message editing could fail silently.Expected Behavior
All agent messages should be reliably delivered, even when Heartbeats and user messages arrive close together.
Environment
Workaround
Using the explicit
messagetool (action=send) appears to work reliably. Only "normal" replies seem affected.