Bug Description
When channels.discord.streaming is set to "block", Discord channels show a persistent "typing" indicator that never clears, even after the agent has finished responding and the message has been delivered.
Environment
- OpenClaw version:
2026.2.24
- Channel: Discord
streaming setting: "block"
Steps to Reproduce
- Set
channels.discord.streaming: "block" in config
- Send a message to any Discord channel with a bound agent
- Agent responds successfully (message delivered)
- Observe: the "Bot is typing..." indicator remains visible in the channel indefinitely
Expected Behavior
The typing indicator should be cleared as soon as the agent's message is delivered.
Actual Behavior
The typing indicator persists indefinitely across all Discord channels, even after successful message delivery. Refreshing the Discord client (Ctrl+R) does not clear it.
Additional Context
- The issue appeared after switching from
streaming: "off" back to streaming: "block"
- Multiple channels affected simultaneously
- The issue persists across gateway restarts
- Verified that no agent session is actively processing (all
stopReason: "stop")
- Switching briefly to
streaming: "off" makes the indicator appear while processing, then clears — suggesting the block mode may not be sending the typing stop signal correctly
Bug Description
When
channels.discord.streamingis set to"block", Discord channels show a persistent "typing" indicator that never clears, even after the agent has finished responding and the message has been delivered.Environment
2026.2.24streamingsetting:"block"Steps to Reproduce
channels.discord.streaming: "block"in configExpected Behavior
The typing indicator should be cleared as soon as the agent's message is delivered.
Actual Behavior
The typing indicator persists indefinitely across all Discord channels, even after successful message delivery. Refreshing the Discord client (Ctrl+R) does not clear it.
Additional Context
streaming: "off"back tostreaming: "block"stopReason: "stop")streaming: "off"makes the indicator appear while processing, then clears — suggesting theblockmode may not be sending the typing stop signal correctly