Summary

When a message originates from one channel (e.g. webchat), the sendChatAction (typing indicator) is sent to the home channel of the agent session (Telegram in this case) instead of the channel that originated the message. This causes the Telegram bot to show "typing..." even when the user is writing from a completely different surface (webchat).

Environment

• OpenClaw version: 2026.2.24 (config written by 2026.2.25)
• Agent: main
• Affected channels: Telegram (home) + Webchat (originating)

Steps to Reproduce

1. Configure OpenClaw with both Telegram and Webchat channels
2. Open a conversation via Webchat
3. Send a message from Webchat
4. Observe the Telegram bot shows typing indicator even though the message came from Webchat

Expected Behavior

sendChatAction should only be sent to the channel that originated the message. If the message came from webchat, Telegram should receive no typing indicator.

Actual Behavior

Every embedded run start log entry shows messageChannel=telegram regardless of which surface triggered the message:

embedded run start: runId=... sessionId=58a77cfb... provider=anthropic model=claude-sonnet-4-6 thinking=off messageChannel=telegram

Even when the session was triggered from webchat. The gateway sends sendChatAction to Telegram for every agent run.

Log Evidence

telegram sendChatAction failed: Network request for 'sendChatAction' failed!

This error repeats every time the agent processes a webchat message — confirming the typing indicator is being sent to Telegram unconditionally.

Impact

• Telegram users see constant "typing..." indicator even when they haven't sent a message
• Creates confusion: user hesitates to send messages thinking the bot is already responding
• Typing indicator leaks internal processing state across channels

Suggested Fix

sendChatAction should be scoped to the originating channel of each run, not the agent's default/home channel. The messageChannel field in the run context should determine where the typing indicator is sent.

Workaround

None currently. User must mute the Telegram bot to avoid the distracting typing indicator.

Reported by a user via OpenClaw webchat. Log analysis performed by the agent itself.