Feature Request: Telegram/Discord Channels support for Cowork Dispatch

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

aCurrently, Claude Code v2.1.80 supports Telegram and Discord channels for pushing events into a CLI session. However, Cowork's Dispatch (mobile interface) does not have equivalent channel/messaging app integration.

Currently users must choose between CLI channels OR Cowork Dispatch, but cannot route tasks intelligently between both from a single messaging interface like Telegram.

Proposed Solution

aAllow Cowork Dispatch to also receive messages from Telegram/Discord, similar to how Claude Code CLI's --channels flag works. This would enable a powerful split workflow:

• Telegram → Cowork Dispatch for cross-tool tasks (browser automation, document generation, image creation, scheduling)
• - Telegram → Claude Code CLI for deep development work (coding, debugging, testing)

Alternative Solutions

aCurrently users must use Claude Code CLI channels OR Cowork Dispatch separately — there is no way to route tasks intelligently between both from a single messaging interface like Telegram or Discord.

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

aA user sends a Telegram message: "Generate a report from my sales data and also fix the bug in my Node.js API."

With this feature:

1. The Telegram → Cowork Dispatch route picks up "Generate a report" and handles document generation via browser automation
2. 2. The Telegram → Claude Code CLI route picks up "fix the bug" for deep coding/debugging work

Without this feature, the user must run two separate sessions and manually split their requests.

Additional Context

_No response_