Problem

When OpenClaw processes internal system messages (exec completions, cron results, subagent reports), it sends sendChatAction: typing to Telegram before the agent turn starts. If the agent responds with NO_REPLY, the typing indicator flashes briefly and disappears — but the user sees constant "typing..." throughout the day.

With 24 cron jobs running (some every 5 minutes), this creates a noisy experience where the bot appears to be perpetually typing even though nothing user-facing is happening.

Expected Behavior

No typing indicator should be sent for:

• System messages from exec completions
• Cron job results being injected into the session
• Subagent completion reports
• Any internal message that is likely to result in NO_REPLY

Proposed Solutions

Option A (config toggle): Add a config option like:

telegram:
  suppressTypingForSystem: true

Option B (smart detection): Delay the typing indicator until the agent has started generating a non-NO_REPLY response. If the response is NO_REPLY, never send the typing action at all.

Option C (message-type aware): Tag inbound system messages with a metadata flag (e.g., internal: true) and skip typing for those.

Environment

• OpenClaw with Telegram channel
• 24 active cron jobs, many running every 5-60 minutes
• Heavy use of subagents and exec background tasks
• All result in typing flashes even when the agent stays silent