Guide · Claude Code

Claude Code without your computer

How to code from your phone, your iPad, or a café — with the full power of your computer.

@maxtechera~6 min read Download PDF

For months now I’ve barely opened Claude Code from my computer. I code from my phone, my iPad, from a café… and all the heavy lifting runs on my machine back home, in Montevideo.

The trick? A Claude Code feature called Remote Control. You leave your most powerful computer running as a “server” and connect from any device — with all your credentials, integrations, and MCPs intact. There are two ways to turn it on, and here are both.

What Remote Control is

It connects claude.ai/code or the Claude app (iOS/Android) to a Claude Code session running on your machine. The key part: Claude keeps running locally the whole time — none of your code moves to the cloud. The web and your phone are just a window into the session that’s already running, with your filesystem, your MCPs, and your config.

🔒 Security

No inbound port is opened on your machine: it only makes outbound HTTPS requests, with TLS and temporary credentials. If your laptop goes to sleep or the network drops, the session reconnects on its own once you’re back online (up to ~10 min).

Requirements

  • Claude Code v2.1.51+ — check it with claude --version.
  • Pro, Max, Team, or Enterprise plan — it doesn’t work with API keys. On Team/Enterprise, an admin has to enable it first.
  • It’s in research preview.
terminal
$ claude update
$ claude --version

How to turn it on: the 2 options

First, two steps that apply to both options:

  1. Log in with claude.ai (claude.ai login, not an API key).
    terminal
    $ claude
    › inside Claude Code:  /login
  2. Accept the “trust” dialog for your folder. Go into your projects folder (mine is ~/dev) and run claude once.
    terminal
    $ cd ~/dev/my-project
    $ claude   # accept the trust dialog

Option A — Server mode (the one I use)

Run this in your projects folder. It stays in server mode and lets you create several sessions at once (up to 32). Ideal for leaving your home computer running as a server.

terminal
$ claude remote-control
✓ Connected · dev · master
  Capacity: 1/32 · space to show QR code · w to toggle spawn mode

Press the space bar to see the QR code, and w to toggle spawn mode. Handy flags:

terminal
$ claude remote-control --name "My Project"
$ claude remote-control --spawn worktree  # each session in its own worktree
claude remote-control running in server mode
claude remote-control connected: capacity 1/32 and “space to show QR code”.
📷 QR code on screenyour phone/app screenshot, save it as img/qr.jpg

Option B — Interactive session

A normal session in your terminal that you also control from your phone (you can type locally and remotely at the same time):

terminal
$ claude --remote-control            # or the shortcut: claude --rc
$ claude --remote-control "My Project"

Already in a session and want to keep going on your phone? Turn it on with the slash command — it carries your full history:

terminal
› inside the session:
/remote-control   # or:  /rc

⚡ Max’s tip

Run Option A on your most powerful computer (the one at home): it has your credentials and integrations, you leave it running as a server, and you carry all that power in your pocket. Option B is great for day-to-day work on a single machine.

Connecting from the web and your phone

With the session active, you have three ways in:

  • Scan the QR code (space bar in server mode) → it opens the session in the Claude app. Don’t have the app? Run /mobile for the download QR code.
  • Open the session URL in any browser → you get in through claude.ai/code.
  • Find it in your session list on claude.ai/code (or tap Code in the app). Remote Control sessions show a computer icon with a green dot when they’re online.
Remote Control session list on claude.ai/code
My list on claude.ai/code: each session shows which machine it’s running on and its capacity.

From the mobile app

Claude app → Code tab → tap the session → keep working with the same context. @ autocompletes files from your project, just like on your computer.

📷 App · Code tab (session list)your phone/app screenshot, save it as img/app-code.jpg
📷 App · session open on the phoneyour phone/app screenshot, save it as img/app-session.jpg

Why it changes everything

  • Power without carrying it: your heavy machine does the work; you carry a phone.
  • Your credentials and integrations: everything lives on the server computer — no reconfiguring anything on each device.
  • From anywhere: café, iPad, phone. Start something and pick it up wherever you are.
  • Same context everywhere: the conversation syncs across terminal, web, and phone.

Tips & tricks

  • The home computer = your server. Server mode (claude remote-control) on your most powerful machine.
  • Turn it on for every session: run /config and enable “Enable Remote Control for all sessions”.
  • Each session in its own worktree: with --spawn worktree they won’t step on each other editing the same files. Press w to toggle.
  • Let your phone notify you: Claude sends you a push when something long finishes. Just ask: “let me know when the tests are done”.
  • Keep the session alive: over SSH, use tmux so it doesn’t die when you close the connection.

Common errors and limits

My session doesn’t show up

Check you’re on v2.1.51+ and using the same account (claude.ai login, not an API key) in the terminal and the app/web.

It died when I closed the laptop

The server machine has to stay on and online. Use your home computer + tmux.

I want several sessions

An interactive session = one remote per process. For several at once, use server mode (Option A).

It disconnected on its own

If the network drops for more than ~10 min, the session expires. And starting an ultra-plan disconnects Remote Control.

Frequently asked questions

Yes. Remote Control works on Pro, Max, Team, and Enterprise. It doesn’t work with API keys. On Team/Enterprise, an admin has to enable it first.
No. Claude runs locally on your machine; the web and your phone are just a window into that session. Traffic goes through the Anthropic API over TLS.
Yes, with server mode (claude remote-control): up to 32. A regular interactive session supports a single remote per process.
The session reconnects on its own once you’re back online (up to ~10 min). After that it expires and you just run the command again.

Claude Code and Remote Control are products of Anthropic. Unofficial guide, based on my workflow and the official documentation.

Download PDF

AI skills for real engineers

Get the practical AI coding workflow notes

Short updates on skills, handoffs, testing and code review — the parts of AI-assisted engineering that survive contact with real code.