Summary

After upgrading to OpenClaw 2026.2.24, Telegram sometimes keeps showing the bot as "typing…" even when the reply is already complete and no run is active.

Environment

• OpenClaw: 2026.2.24
• Runtime mode: local
• OS: macOS 26.3 (arm64)
• Channel: Telegram
• Gateway: loopback (127.0.0.1:18789)

Config tested

• channels.telegram.streaming: partial → later changed to off
• agents.defaults.typingMode: message → later changed to never

Observed behavior

1. Start normal Telegram usage (DM/group), including tool-using runs.
2. At some point, Telegram typing indicator remains active with no visible in-progress response.
3. Restarting gateway (openclaw gateway restart) clears it temporarily.

Expected behavior

Typing indicator should stop as soon as the run/response completes.

Actual behavior

Typing indicator can remain stuck until gateway restart.

Workarounds attempted

• Disable Telegram streaming preview (channels.telegram.streaming: off)
• Disable typing indicator (typingMode: never)
• Restart gateway (temporary relief)

Additional note

This appears related to the recent cluster of Telegram typing-indicator regressions reported around 2026.2.24.