OpenClaw version: v2026.3.2
I am seeing Telegram DM streaming behavior that appears inconsistent with the current docs.
Expected
- With Telegram streaming enabled, a text reply should preview in place.
- For a text-only final reply, the same preview message should become the final message.
- I should not get a second duplicate text box for the same content.
Actual
- I see a streamed preview message first.
- Then OpenClaw sends the same text again as a separate final message box.
- Then the original streamed preview disappears a few seconds later.
Observed config context
channels.telegram.streaming: "partial"
- When
channels.telegram.blockStreaming: true, preview streaming is suppressed entirely.
- When
blockStreaming: false, the duplicate preview/final behavior can occur.
Why this looks like a bug
- Current docs describe Telegram preview streaming as an in-place draft/finalization flow for text replies.
- What I am seeing looks more like the final text is not reusing the preview message as intended.
Questions
- Is this a known Telegram preview -> final fallback issue on
v2026.3.2?
- Is there a recommended config combination for Telegram that keeps preview streaming without duplicate final sends?
OpenClaw version:
v2026.3.2I am seeing Telegram DM streaming behavior that appears inconsistent with the current docs.
Expected
Actual
Observed config context
channels.telegram.streaming: "partial"channels.telegram.blockStreaming: true, preview streaming is suppressed entirely.blockStreaming: false, the duplicate preview/final behavior can occur.Why this looks like a bug
Questions
v2026.3.2?