On March 22, Tencent launched a tool that lets its WeChat platform integrate with OpenClaw agents. The same week, Alibaba, Baidu, ByteDance, and MiniMax all shipped OpenClaw-based products. When four of China's largest technology companies integrate the same open-source project in the same week, you are no longer looking at a developer curiosity. You are looking at infrastructure.
One day later, Anthropic shipped Claude Code Channels.
The timing is not a coincidence. OpenClaw proved, at scale, that there is a massive demand for AI agents accessible through messaging apps. People want to text their AI, not open a browser tab. They want it to act while they're away, not wait to be asked. Channels is Anthropic's answer to that thesis, built natively into Claude Code, with a different architectural bet on how to do it safely.
How OpenClaw went from viral to infrastructure
When Peter Steinberger launched OpenClaw in January 2026, it reached 60,000 GitHub stars within a week. Andrej Karpathy posted about it. Jensen Huang called it "definitely the next ChatGPT" at Nvidia's GTC keynote. The project was renamed twice under trademark pressure and crypto chaos, and kept growing.
The viral developer interest was real. But OpenClaw's bigger story played out elsewhere.
OpenAI and Anthropic don't operate commercially in China. That created a gap: a market of over a billion potential users with access to capable AI models, but no mainstream consumer interface. OpenClaw filled it. WhatsApp, Telegram, WeChat, and Discord are the apps people already have open. An orchestration layer that routes through those apps, runs on local hardware, and connects to any LLM is exactly what that gap needed.
Tencent's WeChat integration on March 22 was the signal. This is no longer a side project. It is a pattern, and the major platforms are adopting it.
What Channels actually does
Channels is a feature in Claude Code, currently in research preview (requires v2.1.80 or later and a claude.ai login). It adds a class of MCP server that can push events into a running Claude Code session, rather than waiting to be queried.
The practical result: you send a message from your phone via Telegram, Discord, or iMessage, and it arrives in your Claude Code session as an event. Claude reads it, does the work, and replies back through the same channel. The answer shows up in Telegram, not the terminal.
The setup flow is deliberate. You install a plugin (Telegram, Discord, or iMessage), restart Claude Code with the --channels flag naming that plugin, and go through a pairing flow where the bot sends you a code and you confirm it. Then you lock down the sender allowlist. Only IDs you have explicitly approved can push messages. Everyone else is silently dropped.
Anthropic also ships a demo called fakechat, a localhost chat UI with no authentication required, designed to let you test the flow before connecting a real messaging platform. It is a good sign that the team thought about onboarding.
The architectural difference that matters
OpenClaw and Channels solve the same user problem with fundamentally different architectures, and the difference has real implications.
OpenClaw is an always-on, always-running local agent. It operates using your credentials continuously, even when you are not at the keyboard. It can message you proactively, triage email at 3am, and run scheduled tasks that span days. The breadth is only limited by what APIs you wire to it. The cost of that breadth is a wide attack surface: in OpenClaw's early weeks, security researchers found 21,639 exposed instances with no authentication.
Channels is session-scoped. Events only arrive while your Claude Code session is open. If you close the terminal, the channel goes silent. There is no always-on agent operating with your credentials in the background. The security posture is meaningfully narrower: no persistent process, no credential exposure outside the active session, and org-level controls for Team and Enterprise users that admins can manage from the claude.ai console.
This is a deliberate trade-off. Channels solves the "I want to reach my AI from my phone while it's working on my machine" problem. It does not solve the "I want my AI to act autonomously while I sleep" problem. OpenClaw does the latter. Whether that is the right problem to solve depends on your risk model.
China's decision to restrict OpenClaw from state enterprises and government agencies is a data point here. When a government bans something from its own offices, the security concern is not theoretical. The hybrid identity problem, where an AI agent operates continuously using human credentials that most security systems cannot distinguish from a real user, is exactly what that ban is reacting to.
What Channels still does not solve
Channels is a research preview, and it shows. It requires Bun as a dependency. It requires a claude.ai login, so console and API key authentication is not supported. The --channels flag syntax may change before it stabilises.
More fundamentally, the always-on gap is real. If you close your laptop, Claude stops listening. For the workflow of asking Claude to keep working while you commute or sleep, Channels does not help unless you run Claude in a persistent background process. That is solvable, but it is extra setup that OpenClaw handles out of the box.
The feature is also Claude Code only. OpenClaw routes to any LLM. If your workflow spans Claude, ChatGPT, and Gemini depending on the task, Channels is not a replacement.
What the signal actually is
The interesting question is not whether Channels is better than OpenClaw. It is not, for many use cases. The interesting question is what it means that Anthropic shipped this at all.
Anthropic is one of the most cautious AI labs on deployment decisions. They do not ship speculative features quickly. That they shipped a native chat-bridge feature in research preview, before it is fully stable, says something about how seriously they take the demand OpenClaw surfaced.
The category of AI accessible via messaging apps that acts while you're away is no longer a third-party experiment. It is a native feature in a flagship developer tool. The next step is obvious: a version that is always-on, fully governed, with enterprise-grade audit trails and identity controls. That product does not exist yet from Anthropic or anyone else. But the direction is now clear.
If your team runs Claude Code, Channels is worth testing. The fakechat quickstart takes ten minutes. The Telegram integration takes twenty. The session-scoped security model is the right trade-off for most professional environments.
And if you are thinking about AI agent governance in your organisation, pay attention to why China banned OpenClaw from its government offices. The hybrid identity problem is not going away. The platforms are starting to take it seriously.