Description
When channels.telegram.streamMode is set to "partial", the final message sometimes appears before the streaming preview edits complete. This causes the user to see what looks like backwards streaming — the full response flashes first, then earlier partial chunks overwrite it.
Environment
- OpenClaw version: 2026.2.15
- Channel: Telegram
- Config:
channels.telegram.streamMode: "partial"
Steps to Reproduce
- Enable `channels.telegram.streamMode: "partial"" in config
- Trigger a multi-paragraph response from the assistant
- Watch the Telegram chat
Expected Behavior
Preview message updates progressively with partial text, then final message replaces it cleanly.
Actual Behavior
Final message appears to send first, then gets overwritten by earlier streaming edits (appears to stream backwards). Eventually resolves to correct text.
Notes
- May be a timing/ordering issue between the final edit and preceding preview edits
- `streamMode: "block"" was not tested — may have similar or different behavior
draftChunk config: { minChars: 50, maxChars: 400, breakPreference: "sentence" }
Description
When
channels.telegram.streamModeis set to"partial", the final message sometimes appears before the streaming preview edits complete. This causes the user to see what looks like backwards streaming — the full response flashes first, then earlier partial chunks overwrite it.Environment
channels.telegram.streamMode: "partial"Steps to Reproduce
Expected Behavior
Preview message updates progressively with partial text, then final message replaces it cleanly.
Actual Behavior
Final message appears to send first, then gets overwritten by earlier streaming edits (appears to stream backwards). Eventually resolves to correct text.
Notes
draftChunkconfig:{ minChars: 50, maxChars: 400, breakPreference: "sentence" }