Claude Code — Remote Control
Drive a Claude Code session running on your local machine from any browser (claude.ai/code) or the Claude mobile app (iOS/Android). Your code, filesystem, MCP servers, and tools all stay local — the web/mobile UI is just a window into that local session.
Why / When to Use
When you want to continue a local Claude Code session from another device (phone, tablet, second laptop) without re-uploading files or losing context. Also useful for monitoring long-running tasks and receiving push notifications when Claude needs input.
Core Concept / Commands
Minimum version
claude --version # must be v2.1.51+Start a Remote Control session
| Method | Command | Notes |
|---|---|---|
| Server mode | claude remote-control | Stays running, accepts multiple concurrent sessions |
| Interactive | claude --remote-control | Full local session + remote access simultaneously |
| From existing | /remote-control (in prompt) | Picks up current conversation |
| VS Code | /remote-control in prompt box | Requires v2.1.79+ |
Connect from another device: open the session URL, scan the QR code, or find the session by name at claude.ai/code.
Push notifications (v2.1.110+)
Claude pings your phone when a task finishes or needs input. Requires the Claude mobile app to be installed.
Key Options / Variants
| Feature | Remote Control | Claude Code on the Web |
|---|---|---|
| Runs on | Your machine | Anthropic cloud |
| Local files / MCP | ✅ Yes | ❌ No |
| Best for | Continuing local work remotely | Fresh tasks, no local setup |
Gotchas
- The local process must keep running — closing the terminal ends the session.
- Network outage > ~10 min causes timeout.
- Starting an ultraplan disconnects Remote Control.
- Some CLI commands (
/mcp,/resume) are local-only and don’t work via remote. - Security model: outbound HTTPS only, no inbound ports opened; short-lived scoped credentials via Anthropic API over TLS.
Source
Conversation: “CC-Remote Control” — 2026-05-16
Updates — 2026-05-17
Always-on Remote Control (built-in setting)
No alias needed — use the built-in config:
/config → enable "Enable Remote Control for all sessions"
This auto-starts Remote Control every time Claude Code launches interactively.
Alternatively, an alias:
alias cc='claude --remote-control'Downsides of always-on Remote Control
- Startup overhead — registers with Anthropic API on every launch, adds ~1–2 seconds
- Internet required — if connection is flaky, Claude Code itself may fail to start
- Outage exits process — if machine loses network for ~10 min, the entire session dies
- Session accumulation — each terminal window registers its own remote session; you’ll accumulate sessions in the list on your phone
- Security surface — your local session is always reachable via Anthropic’s servers while running (TLS + scoped credentials, but still a consideration)
For local LLM dev work, the network dependency is the biggest practical risk — if your LiteLLM proxy or local network has issues, always-on Remote Control adds one more failure point on startup.