Claude Code Remote Control is a feature that connects the claude.ai/code web interface or the Claude mobile app for iOS and Android to a local Claude Code session running on your machine. Designed for developers who use Claude Code as their AI coding assistant, this capability lets you start a task at your desk and seamlessly pick it up from your phone on the couch or a browser on another computer. The core value is maintaining a fully local development environment while gaining the flexibility to interact with that environment from any device, without sacrificing the power of your filesystem, tools, and project configuration. Remote Control ensures that your local environment stays private and responsive, as all processing continues on your machine, so nothing moves to the cloud.
Developers often face interruptions when they need to leave their desk but have a coding session in progress. Closing the terminal means losing context, and cloud-based alternatives may not have access to local resources like specific tools, MCP servers, or project configurations. Remote Control solves this pain point by allowing the session to remain active on the local machine while the developer interacts from a mobile device or another computer. This matters because it eliminates the friction of restarting tasks, re-fetching context, or settling for a restricted remote environment. Developers can step away without anxiety, knowing the session will reconnect automatically when they return, or they can continue directing the work from their phone while away from the desk.
The primary feature group is the ability to use your full local environment remotely. When you start a Remote Control session on your machine, Claude keeps running locally the entire time, so your filesystem, MCP servers, tools, and project configuration all stay available. Type @ to autocomplete file paths from your local project, just as you would in the terminal. This works because the web and mobile interfaces are merely windows into the local session; all execution and file access happens on your machine. The benefit is that you retain the complete power of your local setup, including custom tools, installed packages, and environment variables, without any need to synchronize or duplicate work. This is especially valuable for complex projects with specific dependencies that are not easily replicated in a cloud environment.
A second major feature is the ability to work from both surfaces simultaneously, with the conversation staying in sync across all connected devices. You can send messages from your terminal, browser, and phone interchangeably, and the session remains consistent. Additionally, Remote Control survives interruptions: if your laptop sleeps or your network drops, the session reconnects automatically when your machine comes back online. A connection indicator in the terminal footer and a status panel show the session URL and QR code for quick mobile access. This resilience is crucial for developers who work in fluctuating network conditions or need to move between locations, as they never lose their progress or need to manually restart.
admin
Remote Control also includes mobile push notifications, allowing Claude to send alerts when a long-running task finishes or when it needs a decision from you to continue. You can also request a notification in your prompt, for example \"notify me when the tests finish\". Setup requires installing the Claude mobile app and signing in with the same account, then enabling push via the /config command. On the security side, connections use outbound HTTPS requests only—no inbound ports are opened on your machine. Traffic travels through the Anthropic API over TLS with multiple short-lived credentials, each scoped to a single purpose and expiring independently. This ensures that even while remotely controlling a session, your local security model is preserved.
To use Remote Control, you start a session from the CLI or VS Code extension. The command 'claude remote-control' runs in server mode, displaying a session URL and QR code for connections. Alternatively, add the flag '--remote-control' to an interactive session to make it accessible remotely. In VS Code, type '/remote-control' in the prompt box. Once active, you connect by opening the session URL in any browser, scanning the QR code with the Claude app, or finding the session by name in the session list at claude.ai/code. The session title can be set explicitly or auto-generated from your machine's hostname and a random suffix. You can also enable Remote Control by default for all interactive sessions via /config, so every session automatically registers for remote access.
Concrete use cases for Remote Control include starting a complex refactoring task at your desk and then continuing to monitor and direct it from your phone while traveling. Similarly, a developer can kick off a long-running test suite and receive a push notification when it completes, allowing them to step away without polling. Another scenario is working on a project that requires access to local MCP servers or custom plugins—Remote Control ensures those resources are always available even when accessing from a device without the full environment. The outcome is increased productivity and flexibility: developers maintain their full context and toolchain regardless of their physical location, reducing downtime and context-switching overhead.
Remote Control is designed for developers on Pro, Max, Team, or Enterprise plans who use Claude Code as their primary coding assistant. It supports macOS, Windows, and Linux through the Claude Code CLI (v2.1.51 or later) and VS Code extension (v2.1.79 or later). Team and Enterprise admins must enable the feature via admin settings. The feature is included in existing subscriptions at no extra cost. In summary, Remote Control empowers developers to decouple their physical presence from their development session, offering a seamless way to stay productive while away from the desk. By combining local execution with remote access, it provides the best of both worlds: the power of a local environment and the convenience of mobile interaction.
Developers using Claude Code CLI or VS Code extension who need to continue coding sessions from mobile devices or other computers. Suitable for individual developers on Pro or Max plans, and teams on Team or Enterprise plans where admin enables the feature. Particularly useful for developers who work across multiple locations, travel frequently, or need to step away from their desk without losing context. Also beneficial for teams that want to enable remote collaboration on local sessions while maintaining security and privacy.