Claude Code Dispatch on Telegram vs a room

Claude Code Dispatch is a relay layer that lets you control the Claude Code instance on your computer from a messaging app such as Telegram. What you type in the chat runs on your machine with your files, connected apps and plugins. An agent room is a shared space where several people send work to that agent, each under their own permission, with dangerous actions pausing for the owner and a record of everything.

Both keep the agent local. The difference is what the chat is allowed to do.

What Dispatch is good at

It is the shortest path from a phone to a local session for one person who already lives in Telegram. No new app; the chat is the interface; the machine does the work. For “rerun the tests and tell me” from the train, it is hard to beat.

Where it stops

Dispatch treats the message as the instruction. Three consequences follow when anyone other than you can post.

• Chat membership is the permission model. Whoever can write in the chat can run whatever the agent can run.
• Nothing pauses. “Clean up the old branches” becomes git branch -D with no human between the text and the command.
• No per-person record. A group chat shows who typed, but the agent’s side has no notion of who asked, who allowed, or what it cost.

None of this matters while the chat has one member. All of it matters the moment it has two.

What a room adds

• Per-person permission. Read-only for one person, edit for another, a standing grant for a third.
• Always-pause actions. Push to a shared branch, delete, spend, credentials wait for the owner, with an approval card on the owner’s phone.
• A request id and a timeline for every task, visible to everyone in the room.
• An inbox, so a message sent while the laptop is closed runs when it opens.
• Chat-platform doors. Slack today: each agent gets its own bot, DM it or mention it, approvals land in the owner’s DM. Feishu/Lark and DingTalk follow, bound to the same rooms and rules; Telegram after those. See the Slack connector.

Using both

Dispatch for yourself, a room for others. They do not conflict: both use outbound connections from the machine, and the daemon that serves the room runs as a background service regardless of which terminal Dispatch is attached to.

Frequently asked questions

Can I add approvals to Dispatch? Not in the relay itself. Claude Code’s own permission mode still applies inside the session; a room adds the per-person and always-pause layer on top.

Will muti support Telegram? Slack shipped first, then Feishu/Lark and DingTalk, because that is where our first users’ teams are. Telegram follows. All connectors share one room model.

Is a room slower than a relay? The path is the same length: message → service → outbound poll → machine. The difference is the permission check, which is a database lookup.

For you, a relay. For your team, a room. Give your agent one.