Description

The Telegram typing indicator remains stuck in "typing" state after responses are sent. Restarting Telegram client doesn't help - typing indicator returns shortly after.

Environment

• Clawdbot version: 2a50eadc (current main as of Jan 6, 2026)
• Platform: macOS
• Provider: Telegram

Potential Cause

Bisected to commit 88cb13dc ("Auto-reply: fix typing stop race #270") which removed these lines from ensureStart() in src/auto-reply/reply/typing.ts:

  const ensureStart = async () => {
    if (!active) {
      active = true;
-      runComplete = false;
-      dispatchIdle = false;
    }

These lines were added just before in d5f08897 ("fix: stop typing after dispatcher idle"). Removing them may cause the flags to retain stale values between typing cycles, preventing maybeStopOnIdle() from properly cleaning up.

Steps to Reproduce

1. Send a message to Clawdbot via Telegram
2. Wait for response
3. Observe typing indicator remains active
4. Indicator persists even after restarting Telegram client

Expected Behavior

Typing indicator should stop after the response is sent.

Suggested Fix

Revert commit 88cb13dc or investigate why the flag reset was causing a race condition and find an alternative fix.