Problem

After updating to 2026.2.24, the Telegram typing indicator frequently gets stuck and never clears. This was not happening on 2026.2.22.

Suspected Regression

2026.2.24 changelog includes two typing-related fixes:

• fix(discord): prevent stuck typing indicator #26295 — Discord: seal channel typing keepalive callbacks after idle/cleanup
• fix(typing): guard fireStart against post-close invocation #26325 — Channels: guard typing keepalive start callbacks after idle/cleanup close

The general channels fix (#26325) likely affects Telegram's sendChatAction lifecycle. The sealing/guard logic may have an edge case where Telegram's typing cleanup never fires, leaving the indicator stuck.

Reproduction

1. Have multiple cron jobs running on isolated sessions (we have ~33)
2. Cron jobs complete successfully and return NO_REPLY or deliver via message tool
3. Typing indicator remains visible in DM chat indefinitely
4. Sending a new message or the bot sending a message sometimes clears it, sometimes doesn't
5. Multiple overlapping cron runs make it worse — typing cascades

Environment

• OpenClaw: 2026.2.24
• Channel: Telegram (DM, not forum/topics)
• OS: macOS 15.6 (arm64)
• Node: v22.22.0
• Setup: ~33 cron jobs on isolated sessions, 1h heartbeat on main agent

Previous Version

2026.2.22 did not exhibit this behavior with the same cron configuration.

Workaround

Setting typingMode: "message" in config suppresses the issue but removes typing indicators during legitimate processing.

Related Issues

• Send stop-typing signal when run ends with NO_REPLY #8785 — NO_REPLY doesn't send stop-typing signal
• bug(telegram): typing indicator shows in main chat instead of current forum topic #8936 — typing indicator scoped to wrong chat in forum topics
• TTS: typing indicator stops before audio is sent #5637 — TTS typing lifecycle mismatch