Bug Report

Version: v2026.2.24
Channel: Telegram
Severity: Medium (UX issue, no data loss)

What happens

After updating to v2026.2.24, the "typing..." indicator in Telegram persists indefinitely even after the agent has finished responding and the message was delivered. The session is completed but Telegram keeps showing the agent as typing.

Affected agents

Multiple agents on the same gateway — confirmed on: main session (Aria), finnja agent, nova agent. All triggered after the update to v2026.2.24.

Steps to reproduce

1. Run any agent that takes >30s to respond (long cron job, complex task)
2. Agent finishes and delivers the message successfully
3. Telegram still shows typing... indefinitely

Workaround

Gateway restart (SIGUSR1) clears the stuck typing indicator.

Expected behavior

From the v2026.2.24 changelog entry for #25886/#25882:

Channels/Typing keepalive: refresh channel typing callbacks on a keepalive interval during long replies and clear keepalive timers on idle/cleanup across core + extension dispatcher callsites so typing indicators do not expire mid-inference.

The keepalive timers should be cleared on response completion.

Suspected cause

The keepalive timer introduced/modified in #25886 is not being cleared properly on completion or idle — the fix may have introduced a regression where the timer fires indefinitely after the response is done.

Setup

• OpenClaw v2026.2.24 (docker container, Debian 12, Node v22.22.0)
• Telegram channel
• Multiple isolated agents (cron jobs via sessionTarget: isolated)
• Anthropic/claude-sonnet-4-6 as primary model