Description
After updating to OpenClaw 2026.2.26, messages sent by the agent on Telegram now stream in real-time (new feature!), but some messages appear briefly and then disappear, being replaced by an envelope icon (📩).
Steps to Reproduce
- Update to OpenClaw 2026.2.26
- Have the agent send messages via Telegram channel
- Some messages — particularly those where the agent also uses the
message tool in the same turn — appear momentarily, then vanish and are replaced by an envelope/mail icon
Expected Behavior
Messages should remain visible after streaming completes.
Observed Behavior
- Message streams in (visible text appearing word by word)
- Message disappears
- Replaced by a small envelope icon
- Also observed:
NO_REPLY token leaks into streamed messages (the gateway doesn't filter it from the stream, only from complete messages)
Environment
- OpenClaw version: 2026.2.26
- Channel: Telegram
- Previous version (2026.2.24): Messages arrived as complete blocks, no disappearing behavior
- Streaming appears to be newly enabled in this version
Screenshots
Envelope icon replacing message:
(User reports messages vanishing and being replaced by an icon)
Additional Context
The streaming feature itself is great — just needs the edge cases fixed around message finalization and NO_REPLY token filtering.
Description
After updating to OpenClaw 2026.2.26, messages sent by the agent on Telegram now stream in real-time (new feature!), but some messages appear briefly and then disappear, being replaced by an envelope icon (📩).
Steps to Reproduce
messagetool in the same turn — appear momentarily, then vanish and are replaced by an envelope/mail iconExpected Behavior
Messages should remain visible after streaming completes.
Observed Behavior
NO_REPLYtoken leaks into streamed messages (the gateway doesn't filter it from the stream, only from complete messages)Environment
Screenshots
Envelope icon replacing message:
(User reports messages vanishing and being replaced by an icon)
Additional Context
The streaming feature itself is great — just needs the edge cases fixed around message finalization and NO_REPLY token filtering.