Claude Code Just Got a Remote—And It's Taking Aim at OpenClaw

Here's a workflow problem that's been quietly driving developers up the wall: You tell Claude Code to refactor a module or build out a feature, and then you're just... stuck. Pinned to your desk. Because what if Claude needs approval for something? What if it asks a question? You can't exactly go grab coffee while your terminal is mid-task.

OpenClaw solved this. The open-source tool let you route Claude interactions through WhatsApp, Telegram, Signal—basically any messaging platform—so you could manage your AI coding sessions from your phone. It was clever, it was functional, and according to AICodeKing's latest video, a lot of developers were using it specifically for Claude Code access on mobile.

Well, Anthropic noticed. And their response is Remote Control—a native feature that does roughly the same thing, but with one command instead of a multi-step configuration process. The question isn't whether Remote Control works (it does), but whether it actually makes OpenClaw obsolete, or if we're looking at two tools that just happen to overlap.

What Remote Control Actually Does

The pitch is straightforward: start a coding task on your laptop, walk away, and pick it up from your phone. Everything still runs locally on your machine—your file system, your MCP servers, your project configuration—but you can see and interact with that session from the Claude mobile app or web interface.

There are two ways in. Run claude rc in your terminal to start a fresh remote session, or type /rc inside an existing Claude Code session to take your current conversation mobile. That second option is actually kind of brilliant—if you're already deep into a task with context built up, you don't lose that thread when you switch devices.

Once you start a remote session, Claude Code spits out a session URL and QR code. Scan it with your phone, and boom—you're in. Or if you already have the Claude app open, the session just appears in your session list by name. It's the kind of seamless integration that feels obvious in retrospect.

The persistence is what makes it practical, though. As AICodeKing notes in the video, "If your laptop goes to sleep or your network drops, the session doesn't just die. It stays alive in the background and automatically reconnects when your machine comes back online." That's not a minor detail—that's the difference between a feature you'd actually use and one that sounds good in a demo.

The OpenClaw Comparison (It's Complicated)

So is this the OpenClaw killer? The video creator is pretty clear: it depends what you're using OpenClaw for.

If your use case is specifically "I want to control Claude Code from my phone," Remote Control wins. It's native, it's secure (end-to-end encryption, no self-hosted security management), and setup is literally one command. Compare that to OpenClaw, which requires API keys, messaging platform adapter configuration, and platform-specific dependencies like Signal CLI or Telegram bot tokens.

There's also the security angle. OpenClaw had a remote code execution vulnerability (CVE-2025-25253) that made some people nervous. Not because OpenClaw is inherently sketchy—it's open-source and auditable—but because when you self-host, you're managing all the security yourself. As the video puts it, with Remote Control, "Anthropic has basically said, 'Okay, we'll give you the same mobile workflow, but with native integration, end-to-end encryption, and none of the security headaches.'"

But here's where the comparison gets interesting: OpenClaw does way more than just code. It connects to over 500 apps. It can manage your calendar, browse the web, control smart home devices, send emails—all through your messaging apps. Remote Control only handles Claude Code sessions. As AICodeKing frames it: "It's not a life assistant. It's a coding remote."

So they're not really competing. They're solving different problems that happen to overlap for one specific workflow.

The Costs and Trade-offs

Remote Control requires a Claude Max subscription (Claude Pro users are getting access soon). OpenClaw is completely free—you just pay for whatever API keys you connect to it. And if you really want to stay budget-conscious, you can run local models like Llama 4 or Qwen 2.5 through Ollama. For students or developers on tight budgets, that's not a small difference.

The setup requirements for Remote Control are minimal but specific: Claude Code version 2.1.52 or later, logged in via the /lo command, and you need to have trusted the workspace at least once. There are some quality-of-life features too—you can name sessions with /rename before going remote (helpful when you're juggling multiple sessions), or enable remote control for all sessions automatically via /config.

What This Actually Signals

Here's the part that's more interesting than the feature itself: Claude Code is now doing $2.5 billion in annualized revenue, more than double since the start of the year. And according to the video, 4% of all public GitHub commits worldwide are now authored by Claude Code. That's... a lot of code.

Remote Control isn't some flashy benchmark improvement or a new model drop. It's a quality-of-life feature that solves a real friction point: being tethered to your desk while Claude works. The fact that Anthropic built this—and built it as a direct alternative to a popular open-source tool—suggests they're paying very close attention to how developers are actually using their products in the wild.

The question for most developers isn't "Remote Control or OpenClaw?" It's "What am I actually trying to do?" If you want Claude Code on your phone with minimal setup and maximum security, Remote Control is the obvious choice. If you want a full AI assistant that happens to also control Claude Code sometimes, OpenClaw still has the broader feature set.

But there's a third question that's probably more important: as AI coding tools become more sophisticated, what does "mobile access" even mean? Right now, it means checking in on tasks and giving approvals. As these tools get more autonomous, though, the bottleneck shifts. The limiting factor isn't whether you can see the session from your phone—it's how much you trust the AI to make decisions without you.

Remote Control makes it easier to manage AI coding sessions from anywhere. Whether that's solving the right problem depends on whether you think the future of AI coding is more supervision from more places, or less supervision from anywhere.

—Yuki Okonkwo, AI & Machine Learning Correspondent