Text of code.claude.com › docs › en › channels as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Push events into a running session with channels - Claude Code Docs

Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Channels are in research preview . They require Anthropic authentication through claude.ai or a Console API key, and are not available on Amazon Bedrock, Google Cloud’s Agent Platform, or Microsoft Foundry.

Team and Enterprise organizations must explicitly enable them . A channel is an MCP server that pushes events into your running Claude Code session, so Claude can react to things that happen while you’re not at the terminal. Channels can be two-way: Claude reads the event and replies back through the same channel, like a chat bridge. Events only arrive while the session is open, so for an always-on setup you run Claude in a background process or persistent terminal.

Unlike integrations that spawn a fresh cloud session or wait to be polled, the event arrives in the session you already have open: see how channels compare . You install a channel as a plugin and configure it with your own credentials. Telegram, Discord, and iMessage are included in the research preview. When Claude replies through a channel, you see the inbound message in your terminal but not the reply text. The terminal shows the tool call and a confirmation (like “sent”), and the actual reply appears on the other platform.

If you manage a Team, Enterprise, or Console organization, see Enable channels for your organization . To build your own channel, see the Channels reference . Supported channels Each supported channel is a plugin that requires Bun . For a hands-on demo of the plugin flow before connecting a real platform, try the fakechat quickstart . Telegram Discord iMessage View the full Telegram plugin source . 1 Create a Telegram bot Open BotFather in Telegram and send /newbot .

Give it a display name and a unique username ending in bot . Copy the token BotFather returns. 2 Install the plugin Start Claude Code by running claude in your terminal, then enter this at its prompt: /plugin install telegram@claude-plugins-official If the install fails, match the message Claude Code reports: Marketplace "claude-plugins-official" not found : add the marketplace with /plugin marketplace add anthropics/claude-plugins-official , then retry the install.

Plugin "<name>" not found in marketplace "claude-plugins-official" : your local copy of the marketplace catalog may be out of date. Refresh it with /plugin marketplace update claude-plugins-official , then retry the install. If the retry prints the same message, see Plugin not found in marketplace . When the install asks for an installation scope, choose the user scope option so the plugin is available across all your projects.

Check the install summary: if it reports Run /reload-plugins to apply. , see Apply plugin changes without restarting to make the plugin’s configure command available. 3 Configure your token Run the configure command with the token from BotFather: /telegram:configure <token> This saves it to ~/.claude/channels/telegram/.env . You can also set TELEGRAM_BOT_TOKEN in your shell environment before launching Claude Code. 4 Restart with channels enabled Exit Claude Code and restart with the channel flag.

This starts the Telegram plugin, which begins polling for messages from your bot: claude --channels plugin:telegram@claude-plugins-official 5 Pair your account Open Telegram and send any message to your bot. The bot replies with a pairing code. If your bot doesn’t respond, make sure Claude Code is running with --channels from the previous step. The bot can only reply while the channel is active. Back in Claude Code, run: /telegram:access pair <code> Then lock down access so only your account can send messages: /telegram:access policy allowlist View the full Discord plugin source .

1 Create a Discord bot Go to the Discord Developer Portal , click New Application , and name it. In the Bot section, create a username, then click Reset Token and copy the token. 2 Enable Message Content Intent In your bot’s settings, scroll to Privileged Gateway Intents and enable Message Content Intent . 3 Invite the bot to your server Go to OAuth2 > URL Generator . Select the bot scope and enable these permissions: View Channels Send Messages Send Messages in Threads Create Public Threads Read Message History Attach Files Add Reactions Open the generated URL to add the bot to your server.

4 Install the plugin Start Claude Code by running claude in your terminal, then enter this at its prompt: /plugin install discord@claude-plugins-official If the install fails, match the message Claude Code reports: Marketplace "claude-plugins-official" not found : add the marketplace with /plugin marketplace add anthropics/claude-plugins-official , then retry the install. Plugin "<name>" not found in marketplace "claude-plugins-official" : your local copy of the marketplace catalog may be out of date.

Refresh it with /plugin marketplace update claude-plugins-official , then retry the install. If the retry prints the same message, see Plugin not found in marketplace . When the install asks for an installation scope, choose the user scope option so the plugin is available across all your projects. Check the install summary: if it reports Run /reload-plugins to apply. , see Apply plugin changes without restarting to make the plugin’s configure command available.

5 Configure your token Run the configure command with the bot token you copied: /discord:configure <token> This saves it to ~/.claude/channels/discord/.env . You can also set DISCORD_BOT_TOKEN in your shell environment before launching Claude Code. 6 Restart with channels enabled Exit Claude Code and restart with the channel flag. This connects the Discord plugin so your bot can receive and respond to messages: claude --channels plugin:discord@claude-plugins-official 7 Pair your account DM your bot on Discord.

The bot replies with a pairing code. If your bot doesn’t respond, make sure Claude Code is running with --channels from the previous step. The bot can only reply while the channel is active. Back in Claude Code, run: /discord:access pair <code> Then lock down access so only your account can send messages: /discord:access policy allowlist View the full iMessage plugin source . The iMessage channel reads your Messages database directly and sends replies through AppleScript.

It requires macOS and needs no bot token or external service. 1 Grant Full Disk Access The Messages database at ~/Library/Messages/chat.db is protected by macOS. The first time the server reads it, macOS prompts for access: click Allow . The prompt names whichever app launched Bun, such as Terminal, iTerm, or your IDE. If the prompt doesn’t appear or you clicked Don’t Allow, grant access manually under System Settings > Privacy & Security > Full Disk Access and add your terminal.

Without this, the server exits immediately with authorization denied . 2 Install the plugin Start Claude Code by running claude in your terminal, then enter this at its prompt: /plugin install imessage@claude-plugins-official If the install fails, match the message Claude Code reports: Marketplace "claude-plugins-official" not found : add the marketplace with /plugin marketplace add anthropics/claude-plugins-official , then retry the install.

Plugin "<name>" not found in marketplace "claude-plugins-official" : your local copy of the marketplace catalog may be out of date. Refresh it with /plugin marketplace update claude-plugins-official , then retry the install. If the retry prints the same message, see Plugin not found in marketplace . When the install asks for an installation scope, choose the user scope option so the plugin is available across all your projects.

If the install summary reports Run /reload-plugins to apply. , you don’t need to act on it here, because restarting in the next s

The rest of this page is on the live site.