claude code from telegram, discord or slack

first decide which conversation you mean

there are three different requests hidden in "claude code in slack". you might want to control a session from a slack message. you might want a bot to read team discussion. or you might only want a finished report posted in a channel.

choose one before installing a bridge. a posting action is not evidence that a chat app can control the whole session. access to conversation history is not permission to accept instructions from every person in that conversation. write down who should be able to direct the bot and where its replies should go.

what a do-it-yourself bridge needs to solve

a bridge design would need an incoming-message path, a way to pass the request to the session and a way to return the result. it would also need decisions about:

• identity: which person or channel is allowed to issue a request.
• conversation: how a new message maps to an existing task.
• approvals: where questions reach you and how an answer gets back.
• uptime: which computer keeps the session alive.
• failures: how you tell a lost connection from a completed task.

we don't recommend a particular bridge project. if you cannot inspect how those boundaries work, choose a route you can understand before exposing an important account.

anthropic remote control is a documented route

as of 12 november 2026, remote control connects claude.ai/code or the claude ios and android app to a claude code session on your machine, which must stay on with the claude process running.¹ it doesn't work from telegram, discord or slack; the phone guide compares where the session lives.

dusk bot gives the bot a chat of its own

dusk bot is an app where you keep named bots with jobs, chats, memory and the ai you picked. it runs official ai command-line apps on the machine where the bots live. you text the bot in dusk bot rather than building a channel bridge yourself.²

posting to slack is a different connection

dusk's slack action catalog includes searching messages and sending a message. that can support a separate job where you prepare a result in the bot's chat, then post it to the intended channel. see the slack integration for the app actions.⁴

dusk bot asks before sending unless you choose a daily amount the bot may send on its own. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending.⁸ this does not mean all other app changes ask. keep reading jobs read-only or put "ask me before you change anything" in the instructions.⁵

discord needs its own capability check. the current discord integration catalog includes account and server-membership actions, but does not document a message-posting action. do not assume it matches slack just because both are chat apps.⁶

choose the route you can supervise

use remote control when you want anthropic's documented window into a running local session. use dusk bot when you want your bots' own conversations and a separate app-connection setup. consider a custom bridge only when you need that specific chat entry point and can maintain the missing pieces.

before connecting any route, use the safety guide to decide what the session may reach. a convenient message box is useful, but it is not a reason to widen access or hide approvals.