Summary

Long-running Telegram tasks can appear to have stopped because the typing indicator stops after about 2 minutes. Please consider increasing the default typing TTL to 5 minutes and making it configurable.

Current behavior

Telegram sendChatAction("typing") indicators expire after a few seconds, so OpenClaw refreshes them periodically via session.typingIntervalSeconds (default appears to be 6 seconds).

However, the typing keepalive has a hardcoded TTL of about 2 minutes:

typingTtlMs = 2 * 60_000

After that TTL is reached, the typing loop stops even if the agent task is still running. For complex tasks that take several minutes, Telegram no longer shows any “typing…”/input indicator, which makes the task look stalled or terminated from the user's perspective.

Proposed change

1. Increase the default TTL from 2 minutes to 5 minutes.
2. Expose it as a config option, for example:

{
  "session": {
    "typingIntervalSeconds": 6,
    "typingTtlSeconds": 300
  }
}

Naming alternatives could be typingIndicatorTtlSeconds or typingKeepaliveTtlSeconds if that is clearer.

Rationale

• 2 minutes is too short for moderately complex tasks such as code edits, web/article summarization, multi-tool work, or slow model responses.
• 5 minutes still prevents infinite typing loops if a task gets stuck.
• Making the TTL configurable lets users choose the right tradeoff:
  • shorter TTL for noisy/high-volume group chats
  • longer TTL for private assistant sessions and long-running tasks

Optional guardrails

• Keep a safe maximum, e.g. 15 minutes.
• Preserve the current typingIntervalSeconds behavior separately from the overall TTL.
• Consider different defaults for direct chats vs group chats if needed.