Claude Code Channels: Control Your Agent from Telegram and Discord (2026)
Channels connect your running Claude Code session to Telegram, Discord, and iMessage. Send tasks from your phone, get results in the same chat.
Channels connect your running Claude Code session to Telegram, Discord, and iMessage. Send tasks from your phone, get results in the same chat.
Quick Answer: Claude Code Channels (launched March 20, 2026, research preview) is a plugin-based feature that connects a running Claude Code session to Telegram, Discord, or iMessage. You message your bot, Claude processes the request using your full local environment (filesystem, git, MCP tools), and replies through the same app. Requires Claude Code v2.1.80+, Bun runtime, and a claude.ai Pro or Max subscription.
What Channels are
Channels are MCP server plugins that bridge your Claude Code session to external messaging apps. When you send a message to your Telegram bot, the MCP server forwards it to Claude. Claude processes it with full access to your local files, git repos, and dev tools. The response comes back through the same chat.
Your code stays local. The messaging app is a window into your session, not a cloud-hosted environment.
This is Anthropic's response to what made OpenClaw popular in early 2026. OpenClaw went viral because it let developers message an AI agent through Telegram, WhatsApp, and Discord. Claude Code had no native support for this until Channels shipped.
Recommended skills
skill-router-2
by Shippers · 5
Automatically detect, load, and stack the perfect skills combo for any user requ…
Solo SaaS Architect
by tudor.ai
Automatically builds complete, launch-ready SaaS websites, databases, and secure…
Hooks & Settings for Claude Code
by Markus Isaksson · 15
Master Claude Code's settings hierarchy and hook framework to automate workflows…
Supported platforms
Telegram, Discord, and iMessage are supported as of March 2026. The plugin architecture is designed for expansion. Slack and WhatsApp have been requested by the community.
Each platform has its own setup flow:
Telegram. Create a bot via BotFather, get the bot token, install the Channels plugin, configure the token, and pair your account. You DM the bot and the message lands in your Claude Code session.
Discord. Create a bot in the Discord Developer Portal, install the plugin, configure the token, and pair. Works in DMs and in server channels if you want team access.
iMessage. Added a week after launch. Uses a local relay on macOS.
Channels vs Remote Control
Both let you interact with Claude Code from another device. The difference:
Remote Control routes interaction through the claude.ai web interface and mobile app. Richer UI, one-command setup, but a fixed interface with no push notifications.
Channels use Telegram or Discord as the interface. Native push notifications, more hackable, support team collaboration through Discord servers.
Use Remote Control when you want the full Claude UI on your phone. Use Channels when you want push notifications and team access.
Use cases
Async development. Fire off a task, walk away, get notified when it is done. Channels break the synchronous loop of sitting at your terminal waiting for Claude to finish.
Mobile code review. Ask Claude to review a PR from your phone while commuting. Read the review in Telegram. Approve or request changes.
Team workflows. Set up a Discord channel where team members can send tasks to a shared Claude Code session.
CI/CD notifications. Combine Channels with hooks to get notified in Telegram when a build fails, then ask Claude to investigate without opening your laptop.
Skills that pair well with Channels
When you use Channels, you give Claude short, clear instructions from your phone. Skills that handle common tasks with minimal prompting work best.
git-commit-writer (232 installs) writes conventional commit messages from staged changes. Send "commit my changes" from Telegram and get a clean commit. Free.
code-reviewer (764 installs) runs structured code review. Send "review the latest PR" from Discord. Free.
pr-description-writer (85 installs) generates PR descriptions from your branch diff. Send "write PR description" from your phone. Free.
env-doctor (86 installs) diagnoses startup issues. Send "why won't my project start" from anywhere. Free.
Browse all Claude Code skills on Agensi.
Requirements
Claude Code v2.1.80 or later. Bun runtime (for the MCP server). A claude.ai Pro or Max subscription. Console and API key authentication are not supported in the research preview.
Your Claude Code session must be open to receive messages. Channels are not always-on. Close your terminal and the channel goes dark until you reopen.
How to install skills for Channels workflows
Drop skills into your Claude Code skills directory:
~/.claude/skills/
├── git-commit-writer/
│ └── SKILL.md
├── code-reviewer/
│ └── SKILL.md
Skills load at session startup and work the same way whether you are typing in the terminal or sending messages through Telegram.
Browse all skills for Claude Code on Agensi.
Frequently Asked Questions
What are Claude Code Channels?
Channels are a plugin-based feature that connects a running Claude Code session to Telegram, Discord, or iMessage. You send messages through the app, Claude processes them locally, and replies through the same chat.
When were Channels launched?
March 20, 2026, as a research preview. iMessage support was added about a week later.
Do Channels work with SKILL.md skills?
Yes. Skills load at session startup and work the same way regardless of whether input comes from the terminal or a messaging app.
What is the difference between Channels and Remote Control?
Remote Control uses the claude.ai web UI and mobile app. Channels use Telegram, Discord, or iMessage. Channels offer native push notifications and team collaboration through Discord servers.
Can I use Channels from my phone?
Yes. That is the primary use case. You message Claude through Telegram or Discord on your phone and get results back in the same chat.
Does my Claude Code session need to be running for Channels to work?
Yes. Channels connect to an active local session. If you close the terminal, the channel goes dark. Reopen the session and the channel reconnects.