Research preview · Claude Code

Remote Control:
drive a local session
from anywhere.

Remote Control connects claude.ai/code or the Claude mobile app to a Claude Code session running on your own machine. Start a task at your desk, pick it up from your phone on the couch — the session never leaves your computer.

/remote-control /rc claude remote-control claude --remote-control
How a remote keystroke reaches your files
Click a node to inspect it — or play the data flow to trace a request end to end.
Why it exists

The cloud version moves your work. This one moves you.

Claude Code on the web runs in a cloud sandbox. Remote Control is the opposite trade: the agent keeps running on your machine, so your real filesystem, MCP servers, tools, and project configuration all stay available — and typing @ still autocompletes paths from your local project. You just gain a second (or third) screen to drive it from.

Getting started

Four ways to start a session.

claude remote-control

Runs a dedicated process in your terminal that can host multiple concurrent remote sessions. Press the spacebar to show a QR code.

Best when → you want more than one remote session, or a persistent host you connect to repeatedly.

claude --remote-control "My Project"

A normal interactive Claude Code session running locally that is also reachable remotely. The optional name makes it easy to find in your session list.

Best when → you're working locally now but want the option to step away and continue elsewhere.

/remote-control # or /rc

Turn on Remote Control for a session that's already running, without restarting it.

Best when → you're mid-task and decide you want it on your phone.

/remote-control # in the VS Code prompt box

Available from the VS Code extension (v2.1.79+). Type it straight into the prompt box.

Best when → your local session lives inside the editor.

Connect from another device: open the session URL in any browser, scan the QR code with the Claude app, or pick the session by name in claude.ai/code or the mobile app. To turn it on everywhere, run /config → “Enable Remote Control for all sessions”.

Before you start

What you need.

✓
A Pro, Max, Team, or Enterprise plan. API keys are not supported.
✓
Claude Code v2.1.51 or later. Check with claude --version.
✓
Signed in through claude.ai. Run claude and use /login if you haven't.
✓
Workspace trust accepted. Run claude in the project directory once to clear the trust dialog.
✓
Team / Enterprise only: an Owner must flip the Remote Control toggle in Claude Code admin settings — it's off by default.
✓
Rollout gate: seeing “Remote Control is not yet enabled for your account” means the gradual rollout hasn't reached you yet.
The trade-off

What you gain, what to watch.

You can

  • Use your full local environment: filesystem, MCP servers, tools, project config.
  • Autocomplete local paths with @ from the remote client.
  • Work from several devices at once — the conversation stays in sync.
  • Survive interruptions: it auto-reconnects after a sleep or a dropped network.
  • Get mobile push notifications (v2.1.110+, set up via /config).
  • Run text-output commands remotely: /compact, /clear, /context, /usage, /recap, /mcp, /config, and more.

Keep in mind

  • The local process must keep running — close the terminal or VS Code and the session ends.
  • One remote session per interactive process; use claude remote-control server mode for several.
  • A network outage longer than ~10 minutes times the session out and exits the process.
  • Ultraplan and Remote Control both want claude.ai/code — starting Ultraplan disconnects Remote Control.
  • Some commands stay local-only: /plugin, /resume, and interactive pickers don't work from web/mobile.
Connection & security

Outbound only. Nothing moves to the cloud.

How the connection is secured

  • Your machine makes outbound HTTPS only and never opens inbound ports.
  • It registers with the Anthropic API and polls for work; the server routes messages over a streaming connection.
  • The link uses multiple short-lived credentials, each scoped to one purpose and expiring independently.
  • All traffic travels over TLS — the same transport as any Claude Code session.
  • End a session by closing the local process, disconnecting the remote device, or letting it time out.

Trusted Devices beta · Team / Enterprise

  • If an org enables Require trusted devices, each device must be verified before it can drive Remote Control.
  • Enrollment is a one-time step folded into sign-in.
  • Enrolled members re-authenticate every 18 hours with biometrics (Face ID, Touch ID, Windows Hello) or a passkey.
  • Biometric checks run on-device; Anthropic never receives fingerprints, face, or other biometric data.
  • The rule applies only to Remote Control. Manage or revoke devices at claude.ai/settings/account.
When it won't connect

Quick checks.

/statusConfirm your login method and subscription support Remote Control.
claude doctorRun detailed eligibility checks for the feature.
claude --versionMake sure you're on v2.1.51 or later.
“not yet enabled”The rollout gate hasn't reached your account — separate from any org policy.