Your Laptop Is Your Cloud

Context

Cloud coding sessions run in a fresh VM: they clone the repo, run a setup script and can only reach what the environment's network policy allows. That's right for long or parallel jobs, but the VM can't see your machine's local databases, GPU, VPN, private tools or MCP servers.

Claude Code Remote Control keeps the session on your machine and lets claude.ai/code or the Claude app for iOS and Android drive it. In server mode (claude remote-control) the machine waits for sessions. The Claude app's Code page lists it under Devices, and its Select environment sheet offers it under Remote control, above your Cloud environments. So you start a session on your own machine the same way you start a cloud one.

It's on Pro, Max, Team and Enterprise plans (Team and Enterprise owners must turn it on first). API keys and claude setup-token tokens can't start it.

Architecture

Request flow

1. You run claude remote-control in a project directory. It registers with the Anthropic API over HTTPS and shows a session URL; the spacebar toggles a QR code for the phone.
2. In the Claude app: ☰ → Code. Your machine appears under Devices. Tap New session, open the environment chip and pick your machine under Remote control.
3. A message from the phone goes to the API, which streams it down to the local process.
4. Claude works with your local files, tools and MCP servers. Results, permission prompts and questions go back to every connected device; with push notifications on, the phone buzzes when an action needs you.
5. If the laptop sleeps or the network drops, the session reconnects when the machine is back.

The advantages

1. Your whole machine, not an empty VM. The session sees your files, local databases, GPU, tools, project configuration and MCP servers. Nothing to rebuild in a setup script.
2. Outbound only. The local process makes outbound HTTPS requests and never opens an inbound port. No port forwarding, no dynamic DNS, no VPN into your home network.
3. Parallel sessions without clashes. With --spawn worktree each session gets its own git worktree; server mode runs up to 32 concurrent sessions by default (--capacity).
4. Steer and approve from anywhere. The conversation stays in sync across terminal, browser and phone, and push notifications ask for approvals when Claude needs you.

Where it fits (and where it doesn't)

• Fits: work that needs your local machine (a local database, a GPU, a VPN-only service, private MCP servers or tools) and a machine that stays on and awake.
• Doesn't fit: overnight or long jobs on a laptop that will sleep or close: the local process must keep running. Use a cloud session for those. On a remote box over SSH, start it inside tmux or screen.
• Known limits: server mode exits after roughly 10 minutes without a network connection; the session transcript is stored on Anthropic's servers (code runs and files stay on your machine); and anyone signed into your account can steer the machine, so turn on Trusted Devices (beta: an enrolled device plus a sign-in no older than 18 hours).

Trade-offs

• Depends on the host: closed lid or lost network means paused work.
• Each paired phone or browser becomes a way into your machine; the account is the key (MFA, Trusted Devices, revoke old devices).
• same-dir sessions share one working directory and can edit the same files; use worktree for parallel work.
• Needs a claude.ai sign-in on a Pro, Max, Team or Enterprise plan, not an API key.

Numbers worth knowing

• --capacity default 32 concurrent sessions in server mode.
• Server mode gives up after about 10 minutes without the network.
• --continue / --session-id bring sessions back for about 4 hours after the server stops.
• Trusted Devices: sign-in no older than 18 hours, refreshed with Face ID, Touch ID, Windows Hello or a passkey.
• Illustrative only: the device name my-laptop, the repo habit-app, session names, the terminal output, chat messages and the command on the approval sheet.
• Source: Claude Code docs, Remote Control (checked 2026-10-04).