OpenClaw went viral in January because it nailed one idea: you shouldn’t have to be at your terminal to talk to your AI agent. Message it from Telegram or Discord, let it work, get the answer back in the same chat. Clean.

Anthropic just built that into Claude Code.

Claude Code Channels ships as a research preview in v2.1.80. It’s plugin-based — install the Telegram or Discord plugin, start Claude with --channels, pair your account, and your local session is now reachable from your phone. Messages you send from the chat app arrive inside the running session. Claude does the work against your actual files, git history, and any MCP tools you have set up, then replies back through the same channel.

claude --channels plugin:telegram@claude-plugins-official

The key architectural choice: outbound polling only. Claude’s machine initiates the connection to Telegram or Discord — no inbound ports, no ngrok, no Cloudflare Tunnel. OpenClaw often needed that kind of tunnel setup. Channels sidesteps it.

One honest limitation: this only works while the session is open. Close the terminal, let the machine sleep, and messages from your phone are silently dropped. OpenClaw runs as an always-on daemon and handles that gracefully. Channels requires you to keep a background terminal alive or run Claude on a server.

So where does that leave OpenClaw? Still useful. It supports 50+ platforms (Slack in particular — not in Channels yet), works with non-Claude models, and doesn’t need a live session to stay online. But for my workflow — Claude Code running on a persistent machine anyway — Channels is the simpler path. One less tool to maintain, native integration, no extra auth layer.

The pattern OpenClaw pioneered is now a first-class Claude Code feature.