Bug type

Behavior bug (incorrect output/state without crash)

Summary

In Telegram DMs with channels.telegram.streaming: "partial", a streamed text reply briefly appears as two visible messages at the end of generation. After leaving and reopening the chat, it goes back to a single message.

Steps to reproduce

1. Configure Telegram with partial streaming:

   "channels": {
     "telegram": {
       "streaming": "partial",
       "blockStreaming": false
     }
   }

2. Open a direct message with the bot.
3. Send a normal prompt that produces a text-only reply.
4. Watch the message near the end of streaming.

Expected behavior

The DM should show one visible reply bubble for the entire streaming lifecycle.

Actual behavior

While the draft is being updated, everything looks normal.
When the response finalizes, Telegram briefly shows what looks like a second copy of the same reply.
If I leave the chat and open it again, only one message remains.

So this looks like a draft/finalization display issue in Telegram DM streaming, not a permanent double-send in chat history.

OpenClaw version

2026.3.2

Operating system

Linux 6.1.0-42-amd64 (x64)

Install method

npm global

Logs, screenshots, and evidence

Telegram config:

"channels": {
  "telegram": {
    "enabled": true,
    "dmPolicy": "pairing",
    "streaming": "partial",
    "blockStreaming": false
  }
}

Observed behavior:
- Telegram direct message
- Text-only streamed reply
- Near finalize, a second visible copy appears
- Reopening the chat collapses it back to one message

Impact and severity

Affected: Telegram DM users with partial streaming enabled
Severity: Medium
Frequency: Reproducible
Consequence: Makes the bot look like it sent the reply twice, even though the final chat history only keeps one message

Additional information

This seems different from a true duplicate-history bug because the extra visible message disappears after reopening the chat.

It also seems inconsistent with the current Telegram streaming docs, which suggest DM draft streaming should update in place.