Claude Code Remote Control bridges a local CLI environment to the Claude mobile app and web interface. An outbound-only polling architecture lets you manage running agent tasks remotely while the agent's access to the local filesystem, tools, and MCP servers stays on the host machine — no session migration to the cloud and no inbound ports opened.
Claude Code Remote Control separates the agent’s control surface from its execution environment. You kick off a task in a local terminal, then monitor and steer it from a phone or browser — without moving the workload to the cloud. Unlike a cloud IDE, local context (filesystem, environment variables, and MCP servers) stays live on the host and reachable to the agent.
Architecture and security
The bridge is designed so the host never exposes itself to the network.
Outbound-only polling. The local machine opens no inbound ports. The claude process makes an outbound HTTPS connection to Anthropic’s API and polls for instructions. Only chat messages and tool outputs cross the encrypted bridge — files and MCP servers stay local, and the mobile app is just a remote window into the local session.
Session persistence. Reconnection is automatic. If the host sleeps or the network drops, session state is preserved; when the machine comes back online, the bridge re-establishes itself.
Setup and usage
Requirements
- Plan: Claude Pro or Claude Max.
- Version: Claude Code v2.1.52 or higher.
- Auth: authenticated via
/login.
Commands
| Command | Function |
|---|---|
claude remote-control |
Starts a new remote session and generates a QR code / URL. |
/rc |
Toggles Remote Control from within an active session. |
/config |
Set Enable Remote Control for all sessions to true. |
Why it matters
Remote Control enables a “headless” style of agent management: long-running tasks — refactoring a codebase, running a test suite — are launched at a workstation but supervised and guided from a mobile device while they run. It’s the mobility layer for the parallel, fleet-commander way of working.
- Remote Control Protocol
- Outbound-Only Polling
- Local Context Preservation
- Session Synchronization
Ask Lynx Assist
More Guides
Run disciplined SEO A/B tests in seven steps — one metric, two variations, randomized segments, run to significance, track, analyze the winner, and iterate.
Build a topic cluster in seven steps — select and score a pillar, validate it, map subtopics, align to intent, architect internal links, publish, and measure.
Prepare your site for AI search in five steps — content architecture, entity consistency, E-E-A-T, structured data, and machine-readable structure.
Get your content cited by AI in seven steps — answer capsules, link-free extraction, original data, digital PR, community presence, consistent messaging, and tracking.
A seven-step walkthrough for setting up Google Search Console on a new site — property type, DNS verification, sitemap, GA4 link, users, URL checks, and a monitoring routine.