Claude Code Channels: Control Your Coding Agent from Telegram and Discord

The Problem: Being Tethered to the Terminal

You kick off a long build. A multi-file refactor. A CI debug session. Then you need to leave your desk. Walk the dog. Grab lunch. Sit in a meeting.

For the broader agentic coding map, read Claude Code Agent Teams, Subagents, and MCP: The 2026 Playbook and Why Skills Beat Prompts for Coding Agents in 2026; they connect this article to the surrounding tool and workflow decisions.

The work stalls. Not because the AI cannot continue - it can. But because you are not physically at your terminal to give the next instruction.

Claude Code Channels fixes this. It shipped on March 20, 2026, and it turns Telegram and Discord into remote controls for your running Claude Code session.

How Channels Work

A Channel is an MCP server running locally as a subprocess of Claude Code. The architecture has three parts:

1. Channel plugin (Telegram or Discord) runs on your machine and polls the platform's Bot API
2. Incoming messages get wrapped as <channel> events and pushed into the active Claude Code session
3. Claude processes the request using your local environment, then replies through the channel

Your code stays local. The messaging app is a window into your session, not a cloud-hosted environment. Nothing gets uploaded to Telegram or Discord servers beyond the conversation text.

Setting it up takes one command:

# Install the Telegram channel plugin
claude channel install telegram

# Start Claude Code with the channel active
claude --channel telegram

You will get a pairing code. Send it to your Telegram bot. Once paired, any message you send in that chat goes straight to Claude Code.

What You Can Do From Your Phone

Anything you can do in the terminal session, you can do from the chat:

• Ask Claude to fix a bug, refactor a file, or add a feature
• Check build status or test results
• Review diffs before committing
• Run commands and see output
• Ask questions about the codebase

The interaction feels like texting a developer who has your entire project open. Because that is essentially what it is.

You: "Run the tests for the auth module"

Claude: "Running `npm test -- --testPathPattern=auth`...

3 tests passed, 1 failed:
  FAIL src/auth/token.test.ts
  - refreshToken should handle expired sessions

The failure is in the token refresh logic. The test
expects a 401 response but gets a 403. Want me to
look at the handler?"

You: "Yes, fix it"

The Architecture Under the Hood

Channels use a push-based event model. Traditional MCP tools wait for Claude to call them. Channels invert that - external events arrive in the session whether Claude requested them or not.

The runtime is Bun. All official channel plugins require it. They will silently fail on Node.js with no error message, which caught several early adopters off guard. Make sure Bun is installed before setting up channels.

# Install Bun if you do not have it
curl -fsSL https://bun.sh/install | bash

Security uses a three-layer model:

1. Pairing codes - one-time codes that bind a chat to a session
2. Access controls - allowlists for which users and chats can interact
3. Session isolation - each channel connects to exactly one Claude Code session

Enterprise teams get admin controls for managing access across organizations.

Real Workflows

Mobile code review. You are in a meeting and get a PR notification. Pull out your phone, ask Claude to review the diff, summarize the changes, and flag any issues. All through Telegram.

Overnight builds. Start a long migration before bed. Wake up, check progress from your phone, give the next instruction, go make coffee.

Pair programming from anywhere. Your teammate is at the keyboard. You are on a train. Send instructions through Discord. They see Claude executing in real time.

CI debugging. Tests fail in CI. You are away from your desk. Send the error log to Claude through Telegram, ask it to diagnose and fix.

Tips for Getting the Most Out of Channels

1. Be specific in messages. You do not have the terminal context in front of you, so give clear instructions. "Fix the auth bug" is vague. "The token refresh test in src/auth/token.test.ts is failing - fix the handler" is actionable.

2. Use channels for async work. The best pattern is: start a task, walk away, check in periodically. Do not try to have a rapid back-and-forth from your phone - that is what the terminal is for.

3. Set up notifications. Configure your channel to notify you when Claude finishes a task or hits a blocker. You do not want to keep checking manually.

4. Keep sessions focused. One channel per task. Do not multiplex unrelated work through the same session.

How It Compares to OpenClaw

The open-source project OpenClaw went viral in late 2025 by letting users message AI agents over iMessage, Telegram, WhatsApp, and more. Channels is Anthropic's answer.

The key difference is security. OpenClaw grants deep filesystem access with minimal guardrails, which spawned safety-focused forks. Channels ships with enterprise-grade access controls, session isolation, and Anthropic's safety infrastructure baked in.

FAQ

Do I need to keep my computer running?

Yes. Channels connect to a running Claude Code session on your local machine. If your computer sleeps or the session ends, the channel disconnects. For always-on setups, consider running Claude Code on a remote server or VM.

Is my code sent to Telegram or Discord?

Only the conversation text passes through the messaging platform. Your source code and files stay on your local machine. Claude reads and writes files locally - it sends you summaries and results through the chat, not raw file contents.

Can multiple people connect to the same session?

Yes, with access controls. You can allowlist specific users or group chats. This enables team workflows where multiple developers interact with the same Claude Code session through a shared Discord channel.

Does it work with other messaging platforms?

At launch, Telegram and Discord are officially supported. The channel system is built on MCP, so third-party plugins for Slack, iMessage, and other platforms are possible and some community implementations already exist.

How much does it cost?

Channels itself is free - it is part of Claude Code. You pay for Claude Code usage as normal (either through the Max plan or API credits). The messaging platforms are free to use with bot accounts.