They're Using Claude to Ship Claude (And It Shows)

I've been watching the Claude team work lately, and I can't stop thinking about one thing.

They're dogfooding their own product to build their own product. That's not a hot take. That's just what's happening. And the output is starting to feel like proof of concept at scale.

In the last few weeks alone: Projects in Cowork, Dispatch (the remote-control feature that actually works now), scheduled recurring tasks inside Cowork, Claude Code Channels for controlling your session from Telegram or Discord, two new flagship models in Sonnet 4.6 and Opus 4.6, Excel and PowerPoint add-ins that now share full conversation context, a plugin marketplace, a persistent agent thread for Pro and Max users, and inline custom visualizations in chat.

Count those up. That's not a quarter's worth of releases. That's a few weeks.

---

The Meta Part Is the Point

There's something beautifully recursive happening here. You're using an AI assistant to build features that make the AI assistant more useful. Every improvement compounds. Every workflow they unlock internally probably turns into a shipped feature two weeks later.

It's Inception, but for product development. Dream within a dream, except the dream is a Claude Code session running scheduled tasks overnight while someone sleeps in San Francisco.

I've used the term "dogfooding" professionally for years. Most teams give it lip service. They use the product occasionally, file a ticket or two, and call it good. What Anthropic appears to be doing is different. The pace of iteration suggests they're living inside these tools, hitting real edges, and shipping fixes faster than the release notes can keep up.

That's not marketing. That's what it looks like when a team actually eats the food.

---

The Features That Signal Something Bigger

Claude Code Channels caught my attention the most. Announced March 20, 2026 as a research preview, it ships with Telegram and Discord support first, with a plugin architecture designed to expand from there. The idea is straightforward: you message a bot from your phone, and the Claude Code session running on your machine picks it up, executes the work, and replies back through the same channel. It's two-way. Claude reads the event and responds through the channel. Your presence at the terminal is optional.

I know exactly what that setup looks like. I've been building it myself.

My OpenClaw project, an always-on personal agent named Roci running on an AWS EC2 instance behind Tailscale, exists precisely because this gap existed. (Roci is short for Rocinante, the ship from The Expanse, itself named after Don Quixote's horse. A creature that kept moving regardless of whether the quest made sense. For an always-on agent, I couldn't think of a better namesake.) If you wanted a persistent AI worker you could message from anywhere and have it do real work while you stepped away, you had to roll it yourself. Axiom is my sandbox for that problem: a SOUL.md, a USER.md, a TOOLS.md, identity configuration, the works. Infrastructure I provision and maintain, trade-offs I make consciously.

Claude Code Channels is Anthropic shipping that same idea as a first-party, five-minute setup.

The architectural choice here is worth noting. The channel plugin runs locally on your machine and polls the messaging platform's Bot API. No inbound port opened on your machine. No webhook endpoint exposed to the public internet. No reverse proxy needed. Compare that to what it takes to route traffic through a Tailscale mesh to an EC2 instance. Both approaches solve the same problem. One of them involves considerably more yak shaving.

This is the tell. When the tool you've been building on your own time starts shipping as a native product feature, you're not ahead of the curve anymore. You're validating it. OpenClaw, Roci, every homebuilt persistent agent hack out there: demand signals. Anthropic read them.

What Roci taught me is that the hard part isn't the messaging layer. It's context persistence, identity configuration, and deciding what you trust the agent to do unsupervised. Those problems don't go away with Claude Code Channels. They just become accessible to more people, which shifts the interesting work upstream. The real architecture question becomes: what does your agent do while you're not watching, and what guardrails do you put around that?

Because Channels is built on MCP, the community can build connectors for Slack or WhatsApp without waiting for Anthropic to ship them. That's not a small design choice. That's Anthropic acknowledging they can't cover every surface themselves, so they're making the protocol extensible from day one. OpenClaw's whole appeal was reach: iMessage, WhatsApp, Telegram, Slack, all in one personal AI worker. Anthropic's answer isn't to match every surface. It's to build the protocol layer and let the community fill the gaps.

The scheduled recurring tasks in Cowork carry the same signal. Someone hit a real problem: "I want this to run on a cadence without me triggering it manually." They built the solution, then shipped it. That loop is fast.

Projects in Cowork and Dispatch point at something else entirely. Persistent, organized workspaces with their own files, context, instructions, and memory. A remote control for your desktop agent that you pair from your phone via QR code and use from anywhere your Mac stays awake. These are harder problems. The fact that they're shipping alongside the more tactical features suggests depth of execution, not just velocity.

---

What This Means for Builders Like Me

I've been building with Claude Code since the early days of the product. I've watched it get meaningfully better, not in a "we added a setting" way, but in a "the fundamental workflow just shifted" way.

That's rare. Most tools plateau. They hit good enough and stay there because the incentive to keep pushing drops off.

The Anthropic team doesn't have that problem. Every improvement they make to Claude is an improvement to the tool they use to make improvements to Claude. The flywheel is real, and it is spinning fast.

My practical take: if you're a builder who hasn't revisited Claude or Claude Code in the last 30 days, you owe yourself 20 minutes this week. The tool you used then is not the tool you'll open today.

And by the time you finish reading this, they've probably shipped something else.

---

A Note on the Remote Control Fix

Dispatch works now. That's all I'll say. Sometimes the most important release note is the one that just says: fixed.

---