Description
Every assistant response is delivered twice to Telegram. The session log shows a single outbound message, so the duplication is happening in the delivery layer, not in the agent.
Steps to Reproduce
- Run any agent session over Telegram (direct chat)
- Send a message and receive a response
- The same response appears twice in Telegram
Expected Behavior
Each assistant response is delivered once.
Actual Behavior
Each assistant response is delivered twice (exact duplicate, back-to-back).
Environment
- Channel: Telegram
- Agent: main session (direct chat)
- OpenClaw version: v2026.2.24
Additional Context
- Verified the session JSONL log — only one assistant message entry per turn
- The agent is not using the
message tool (which could cause double-send if NO_REPLY is missed)
- Duplication is consistent, not intermittent
- Delivery queue at
~/.openclaw/delivery-queue/ shows no relevant retries for these messages
This points to the Telegram outbound dispatch layer sending the message twice, possibly a retry on an ACK timeout that doesn't check for prior successful delivery.
Description
Every assistant response is delivered twice to Telegram. The session log shows a single outbound message, so the duplication is happening in the delivery layer, not in the agent.
Steps to Reproduce
Expected Behavior
Each assistant response is delivered once.
Actual Behavior
Each assistant response is delivered twice (exact duplicate, back-to-back).
Environment
Additional Context
messagetool (which could cause double-send ifNO_REPLYis missed)~/.openclaw/delivery-queue/shows no relevant retries for these messagesThis points to the Telegram outbound dispatch layer sending the message twice, possibly a retry on an ACK timeout that doesn't check for prior successful delivery.