What Is Claude Code Remote Control?
Claude Code Remote Control is a new feature that connects your local Claude Code terminal session to your phone, tablet, or any browser. Start a coding task at your desk, walk away, and continue it from your couch using the Claude mobile app.
The key difference from cloud-based coding: everything runs locally. Your filesystem, MCP servers, tools, and project configuration stay on your machine. The mobile interface is just a window into your running session.
How It Works
Your Machine (terminal) Anthropic API Your Phone
┌─────────────────────┐ ┌───────────┐ ┌──────────┐
│ claude remote-control│ ──TLS──▶│ Routes │◀──TLS── │ Claude │
│ │ │ messages │ │ App │
│ Local filesystem │ └───────────┘ └──────────┘
│ MCP servers │
│ Project config │
└─────────────────────┘No port forwarding. No VPN. No SSH tunnels. Claude Code makes outbound HTTPS requests only — it never opens inbound ports on your machine. The Anthropic API routes messages between your local session and whatever device you're using.
Getting Started
Requirements
- Claude Pro or Max plan (not available on Team/Enterprise yet)
- Claude Code installed and authenticated via
/login - Claude mobile app — iOS or Android
Start a New Remote Session
Navigate to your project and run:
claude remote-controlThis displays a session URL and a QR code (press spacebar to toggle). Scan the QR code with your phone to connect instantly.
From an Existing Session
Already mid-conversation? Use the slash command:
/remote-controlOr the shorthand:
/rcYour full conversation history carries over. Tip: use /rename first to give the session a descriptive name so you can find it on your phone.
Connect from Another Device
Three ways to connect:
- Scan the QR code — fastest, opens directly in the Claude app
- Open the session URL — works in any browser at claude.ai/code
- Find it in the app — remote sessions show a computer icon with a green dot when online
Real-World Use Cases
The "Deploy from Dinner" Workflow
You're running a deployment at your desk. The build is going to take 20 minutes. Walk to dinner, and when the build finishes, approve the next step from your phone. No rushing back to your laptop.
Code Review on the Couch
Start reviewing a PR at your desk with full context — local repo, test runners, linters. Move to the couch and continue asking Claude questions about the code, running tests, and suggesting changes.
On-Call Incident Response
Get paged at 2 AM. Instead of opening your laptop, scan the QR code on your phone and start debugging immediately. Claude has access to your full local environment — logs, configs, deployment scripts.
Always-On Mode
Don't want to run /remote-control every time? Enable it globally:
- Run
/configinside Claude Code - Set Enable Remote Control for all sessions to
true
Now every Claude Code session is automatically available from your phone.
Security Model
- All traffic goes through the Anthropic API over TLS — same security as normal Claude Code usage
- Multiple short-lived credentials, each scoped to a single purpose with independent expiration
- No inbound ports opened on your machine
- Session data stays local — the phone is just a remote display
Limitations to Know
| Limitation | Detail |
|---|---|
| One remote connection | Each session supports one remote connection at a time |
| Terminal must stay open | If you close the terminal, the session ends |
| Network timeout | ~10 minutes of network loss kills the session |
| Plan requirement | Pro or Max plan only (no API keys) |
Remote Control vs Claude Code on the Web
Both use the same claude.ai/code interface, but they're fundamentally different:
| Remote Control | Claude Code on Web | |
|---|---|---|
| Execution | Your machine | Anthropic cloud |
| File access | Your local filesystem | Cloud sandbox |
| MCP servers | Your local servers | Not available |
| Best for | Continuing local work remotely | Starting fresh without local setup |
Use Remote Control when you're mid-task and want mobility. Use Claude Code on the web when you want to spin up something new without cloning a repo.
What This Means for Developer Workflows
Remote Control solves a real friction point: context switching between devices kills flow. Previously, if you walked away from your desk, you either lost your coding context or set up complex SSH/tmux/mosh chains.
Now it's: run one command, scan a QR code, keep going. Your full environment — files, tools, MCP servers, conversation history — travels with you.
Combined with Claude Code's $2.5 billion annualized run rate as of February 2026, it's clear that AI-assisted coding is no longer experimental. Remote Control is the kind of quality-of-life feature that makes daily use seamless.