How to Use Claude Code Remote Control: Complete Step by Step Guide
By Braincuber Team
Published on April 21, 2026
Claude Code Remote Control creates a live bridge between your running local session and claude.ai or the Claude mobile app. The process continues running on your machine, and your browser or phone simply becomes another interface to it. This comprehensive guide walks you through setup, connection methods, and advanced configurations.
What You'll Learn:
- What Claude Code Remote Control is and how it works
- Architecture and security model explained
- Prerequisites and authentication setup
- Three methods to start a Remote Control session
- Connecting via browser and mobile device
- Advanced configurations and concurrent sessions
- Troubleshooting common issues
What Is Claude Code Remote Control?
Claude Code is Anthropic's terminal-native AI coding assistant. Unlike browser chatbots or IDE extensions, it runs directly inside your terminal and operates on your local files. Remote Control extends that model by adding a synchronization layer between your running local session and the Claude mobile app or any web browser.
When Remote Control starts, your local Claude Code process establishes an outbound HTTPS connection to the Anthropic API and registers the session. It then polls that API for incoming instructions rather than opening any listening ports on your machine. This design means your machine never opens inbound ports or exposes services to the internet.
Key Security Point
Your phone or browser does not execute code or access your files directly. It simply renders the conversation and sends prompts. The actual execution, reading files, running commands, and accessing MCP servers continues to happen entirely on your machine.
Claude Code Remote Control vs OpenClaw
OpenClaw is currently the most starred personal autonomous AI assistant project on GitHub. It exposes an AI agent through messaging channels such as WhatsApp, Telegram, Discord, and Slack.
Claude Code Remote Control follows a different model. Instead of routing commands through messaging platforms, it connects your browser or phone directly to your local Claude Code session. The remote device becomes a live interface to that running terminal session.
| Feature | Claude Code Remote Control | OpenClaw |
|---|---|---|
| Connection Model | Direct to local session | Via messaging platforms |
| Execution | Local machine | Remote agent |
| Security | Outbound HTTPS only | External integrations |
| Use Case | Extend live coding session | Multi-channel automation |
Claude Code Remote Control Prerequisites
Before using Claude Code Remote Control, you need a working Claude Code installation and a paid claude.ai account. Remote Control is currently available for claude.ai Pro and Max subscribers.
| Plan | Price | Remote Control |
|---|---|---|
| Free | $0 | Not included |
| Pro | $20/month | Included |
| Max | $100/month | Included (higher limits) |
How to Install Claude Code
Install Claude Code using the native installer, which is faster than the legacy npm method since it requires no Node.js dependency and auto-updates in the background.
macOS / Linux
curl -fsSL https://claude.ai/install.sh | bash
Windows PowerShell
irm https://claude.ai/install.ps1 | iex
Getting Started With Claude Code Remote Control
With Claude Code installed, there are three checks to clear before Remote Control will work reliably.
Check Your Claude Code Version
Remote Control requires Claude Code v2.1.51 or later. Run claude --version to verify. If needed, update with claude update.
Authenticate and Verify Subscription
Remote Control requires a Pro or Max subscription. Run /status to check your current login. Use /login to change accounts if needed.
Establish Trust
When you run Claude Code in a project for the first time, it asks whether you trust the workspace. You must accept this dialog to enable Remote Control.
Starting Your First Remote Session
There are three ways to initialize a Remote Control session.
Method A: Server Mode
Server mode is the right choice when you want to dedicate a terminal process entirely to serving remote connections with no local interaction.
claude remote-control --name "my-session"
Method B: Interactive Session with Remote Control
If you want to keep working in the terminal while making the session accessible from another device, use the --remote-control or --rc flag.
claude --remote-control
Method C: On-the-Fly Upgrade Mid-Session
The most useful method when you are already deep into a session and suddenly need to step away. Simply type /remote-control or /rc inside the running session.
/remote-control
Pro Tip
Use /rename before enabling Remote Control. A session named "sure, go ahead" is hard to find on your phone. Name it something descriptive like "refactoring-task" or "bug-fix".
Connecting Your Devices
Using a Browser
As soon as you start Remote Control in your terminal, Claude Code prints a session URL. Copy that URL and open it in any browser to land directly inside the same live session at claude.ai/code.
Using a Mobile Device
For phone access, scanning a QR code is the fastest route. In the terminal where your Remote Control session is running in server mode, press the Spacebar to display the QR code, then scan it with your phone.
If you started Remote Control from an interactive session using --rc or /rc, open the Claude mobile app, go to the Code tab, and locate your session by name in the session list.
Advanced Configurations
Enable Remote Control Globally
If you want Remote Control available by default for every session, run /config inside Claude Code and set "Enable Remote Control for all sessions" to true.
Running Concurrent Sessions
By default, one Claude Code process serves one remote connection. The --spawn worktree flag in server mode enables multiple concurrent sessions. Your project needs to be a Git repository for this to work.
claude remote-control --name "task-1" --spawn worktree
Troubleshooting and Limitations
| Issue | Solution |
|---|---|
| Terminal closes | Run session in tmux to survive window closures |
| Network timeout | 10 minute cutoff - session ends if network unavailable |
| Approvals required | Every tool call needs manual approval even remotely |
| One device at a time | Only one device can connect unless using --spawn |
Best Practice
Front-load your instructions heavily before stepping away. The more context, edge cases, and decision branches you provide upfront, the fewer times the agent stops to ask for approval.
Frequently Asked Questions
What is Claude Code Remote Control?
Claude Code Remote Control creates a live bridge between your running local session and the Claude mobile app or browser, allowing you to control your terminal session from another device.
Does Anthropic have access to my code during Remote Control?
No. According to Anthropic, Remote Control sessions are end-to-end encrypted and Anthropic does not see your code. Your files and MCP servers never leave your machine.
Can multiple devices connect to the same session simultaneously?
No. Only one device can be connected to a given session at once outside of server mode. Use --spawn worktree for concurrent sessions.
Can I start a new session from my phone without my laptop?
No. Remote Control requires you to first start the session on your computer. Once started, you can continue and redirect it remotely.
What subscription is required for Remote Control?
Remote Control requires claude.ai Pro ($20/month) or Max ($100/month). The free plan does not include this feature.
Ready to Go Mobile with Claude Code?
Claude Code Remote Control lets you extend your local development session to your phone or browser. Start with the methods in this tutorial, enable Remote Control for your common projects, and enjoy the flexibility of controlling your AI coding assistant from anywhere.