[zellwk]

Depends on #97 — merge that first. Without it parse_status_line returns None while a tip block is showing, and the indicator drops out mid-turn.

Problem

The typing indicator fires only when the status text contains esc to interrupt:

if "esc to interrupt" in status_text.lower():
    await bot.send_chat_action(chat_id=chat_id, action=ChatAction.TYPING)

Claude Code moved that string out of the status line and into the footer hint below the input box, so the condition is now never true and the indicator never appears:

✳ Gitifying… (2m 1s · ↓ 6.5k tokens)      <- status line, parsed, no "esc"
────────────────────────────────────────
❯
────────────────────────────────────────
  ⏸ manual mode on · esc to interrupt     <- footer, never parsed

The status line samples in #52 show the same thing — none of them carry the string.

Even before the UI change, this only half worked: Telegram expires a chat action after ~5s, and a single send_chat_action fired per status change. A long turn showed the dots briefly and then went silent.

Fix

Drive the indicator from status polling, which already runs once a second and is the only place that knows whether a session is mid-turn — a parsed status line means working, no status line means idle. A keepalive task re-sends the action every 4s and is cancelled on idle, on status clear, on topic cleanup, and at shutdown.

Two smaller things fixed along the way:

• the chat action now carries message_thread_id, so it lands in the right forum topic rather than the group's General (every other send in message_queue.py already passes it via _send_kwargs)
• a failed action logs at debug instead of except Exception: pass

Note for reviewers

#52 also touches src/ccbot/handlers/status_polling.py. The overlap is small — this adds three lines next to the existing parse_status_line call, that one adds throttling around the enqueue — but whichever merges second will want a look.