Yesterday morning I fixed a production bug from the subway. I typed a single message in Telegram, and Claude Code patched the file, ran the tests, and committed the fix. My laptop stayed in my bag the entire time.
On March 20, Anthropic released Claude Code Channels as a research preview — a plugin-based feature that connects your Claude Code sessions to Telegram and Discord. You send messages from the app, Claude processes them using your local dev environment, and replies in the same chat. Five days in, it has reshaped how I work in ways I didn't expect.
The Morning Ritual Changed
I used to start my day by opening VS Code and checking overnight CI results. Now my alarm goes off at 7 AM and the first thing I see in Telegram is a message from Claude: "Build passed, 142 tests green, coverage 87.3%." On good days I just nod and make coffee.
The real value shows up on bad days. "3 tests failed. Timeout at user-auth.test.ts line 47." I type "show me that test" right there in Telegram. Claude reads the file from my dev machine, explains what's happening, and suggests a fix. I reply "do it" — still in bed, still half asleep — and by the time I'm showering the build is green again.
This isn't hypothetical. This is Tuesday.
Setup Is Comically Simple
You need Claude Code v2.1.80 or newer and a claude.ai Pro, Max, or Enterprise subscription. Run claude channels add telegram in your terminal, paste the bot token from BotFather, and you're connected. Discord is the same flow with claude channels add discord. The whole process takes about three minutes.
Under the hood, Channels is built on MCP — Model Context Protocol — the open standard Anthropic published in 2024. If you've already used MCP servers for database access or API integrations, Channels is just another MCP server that happens to bridge a messaging platform to your dev environment. The architecture means adding new platforms doesn't require rearchitecting anything; it's why the community is already requesting Slack, WhatsApp, and iMessage support.
Post not found or has been removed.
The Commute Became a Sprint
My 40-minute subway ride used to be podcast time. Now it's the most productive coding window of my day — except I'm not coding. I'm delegating.
"Check the 3 review comments on PR #47 and address each one." Claude fetches the comments through GitHub's API, reads the relevant source files, makes the changes, and commits. I review the diffs in Telegram and send "LGTM." By the time I scan my badge at the office, yesterday's code review is done and merged.
The old version of this took 30 minutes minimum. Open VS Code, navigate to the PR page, read each comment, context-switch between files, make edits, test locally, commit, push. Now it happens between Gangnam and Sadang station.
Build Failures That Actually Get Fixed
Before Channels, my relationship with CI notifications was adversarial. GitHub Actions would send emails. I'd ignore most of them. Occasionally something critical would slip through and I'd find out two hours later from a teammate on Slack.
Now Claude sends me a Telegram message the moment a build breaks. Not just "build failed" — the full context. Which test failed, the exact error message, the probable root cause, and a suggested fix. I reply "fix it" and Claude patches the code, pushes the commit, and reruns CI. The entire loop — detection, diagnosis, repair, verification — happens in a chat window on my phone.
This alone makes Channels worth adopting. The feedback loop between "something broke" and "it's fixed" shrank from hours to minutes.
What My Actual Day Looks Like Now
At 7 AM I check overnight results in Telegram from bed. Failed builds get fixed before I leave the house. During my 40-minute commute I review PRs and delegate fixes. At the office I start fresh on new features because the maintenance backlog is already handled.
At lunch I send "create a feature branch for the payment refactor and scaffold the basic structure." By the time I'm back from eating, boilerplate and file structure are ready. After work, during my evening walk, I dictate tomorrow's first tasks. Morning-me finds a prepped workspace.
The pattern is clear: Channels turns dead time into productive time. Not by making you work more, but by letting Claude handle the mechanical parts asynchronously while you do other things.
Discord Makes It a Team Sport
Solo use is powerful. Team use is where it gets genuinely interesting.
Set up a Discord channel with Channels connected, and any team member can ask Claude questions about the codebase. "Why does the payment webhook retry 5 times?" Claude checks the source, finds the retry config, and answers with the exact file path and line number. No one had to interrupt anyone. No one had to context-switch. The answer just appeared in the channel everyone was already watching.
During a sprint, someone posted "the staging API is returning 500 on /api/orders." Claude checked the server logs, identified a null pointer in the order serializer, and posted the fix — all in the Discord thread. The engineer applied the patch and confirmed it worked, all without leaving Discord. The total resolution time was under four minutes.
The MCP Foundation Matters
Everything I've described works because of MCP. Claude Code Channels operates as an MCP server that connects to your local file system, Git, terminal, and any other MCP servers you have configured. The messaging platform is just a thin transport layer on top.
This architecture is why VentureBeat called Channels an "OpenClaw killer." OpenClaw offered remote agent control through a dedicated interface. Claude Code offers the same control through apps developers already have open — Telegram, Discord, eventually Slack. The barrier to adoption drops to zero.
Post not found or has been removed.
Five Days of Honest Assessment
Not everything is perfect. The research preview has rough edges. Long code blocks sometimes get truncated in Telegram's message size limits. Response latency spikes occasionally, especially during peak hours. Complex multi-file refactors still need a proper IDE session where you can see the full picture.
But roughly 60-70% of my daily development tasks — code reviews, bug fixes, build monitoring, scaffolding, simple feature work — now happen through Telegram. The remaining 30-40% still needs VS Code and a proper screen. That ratio will shift as the feature matures.
The deeper realization is about development itself becoming asynchronous. Code doesn't stop moving when I step away from my desk. Ideas become implementations within seconds of forming. The gap between "I should fix that" and "it's fixed" collapsed.
The Interface Is Shifting
A decade ago, the terminal was the developer's primary interface. Five years ago, VS Code took over. Now messaging apps are entering the picture — not as replacements, but as extensions that cover the 70% of development work that doesn't require staring at a full IDE.
Claude Code Channels is the first tool that makes this practical. It won't replace your editor. It will make you wonder why you used to open it for things that could've been a chat message.
Five days in, the question isn't whether messaging will become a developer interface — it's how we ever tolerated the alternative.
Sources
- Anthropic Claude Code Channels Official Docs
- VentureBeat — Anthropic just shipped an OpenClaw killer
- MacStories — Hands-on with Claude Code Channels
What's the first task you'd delegate to a Telegram chat instead of your IDE?
Top comments (0)