Summary

When channels.telegram.streaming is set to partial, the Telegram typing indicator ("typing...") continues showing indefinitely in Telegram DM after the bot has finished responding. The indicator never clears until the user sends another message.

Steps to reproduce

1. Set channels.telegram.streaming to partial in openclaw.json
2. Restart the gateway (openclaw gateway restart)
3. Send any message to the bot in a Telegram DM
4. Bot responds correctly with streamed text
5. Observe the typing indicator in Telegram after the response is fully delivered

Expected behavior

Typing indicator should stop once the bot's response is fully delivered.

Actual behavior

Typing indicator persists indefinitely after the response is complete. It never stops until the user sends another message. The bot's actual text response is delivered correctly — only the typing indicator fails to clear.

OpenClaw version

2026.2.24

Operating system

macOS 26.3 (arm64)

Install method

npm global

Logs, screenshots, and evidence

Impact and severity

• Affected: All Telegram DM users with streaming set to partial
• Severity: Annoying (cosmetic but confusing — users think the bot is still processing)
• Frequency: 100% reproducible on every message
• Consequence: Misleading UX; users wait thinking the bot is still working when it has already finished

Additional information

No typingMode or typingIntervalSeconds overrides are set (using defaults). The default typingMode is unset (legacy behavior: typing starts immediately in DMs). Setting streaming to off resolves the stuck indicator but removes streaming functionality.

Telegram config:

{
  "streaming": "partial",
  "dmPolicy": "pairing",
  "groupPolicy": "allowlist"
}

Node 22.22.0, gateway running as LaunchAgent.