Claude Code Remote Access

Key Features

• •Multi‑surface connectivity: start a session with `claude remote-control` and connect via session URL, QR code, or the session list at claude.ai/code. Supports simultaneous interaction from terminal, browser, and phone, keeping the conversation in sync across all devices.
• •Full local environment access: Claude runs entirely on your machine, giving you your exact filesystem, MCP servers, tools, and project configuration remotely. File path autocompletion (`@`) works from the web and mobile interfaces just like at the terminal.
• •Interruption survival and auto‑reconnect: if your laptop sleeps or the network drops, the session reconnects automatically when your machine comes back online, preserving conversation history without data loss.
• •Server‑mode concurrency: `claude remote-control` with `--spawn` serves multiple sessions, each optionally isolated in its own git worktree, with adjustable capacity (`--capacity N`). Ideal for shared build machines or team environments.
• •Mobile push notifications: Claude can push to your phone when a long task finishes or a decision is needed. Configure proactive and action‑required notifications separately, and use `CLAUDE_CLIENT_PRESENCE_FILE` to suppress notifications while you’re at the machine.
• •VS Code integration: type `/remote-control` in the Claude Code extension to enable remote access. A banner shows connection status, and a button opens the session directly in your browser, with automatic disconnection when you close the banner.
• •End‑to‑end security: only outbound HTTPS connections, no open local ports, all traffic over TLS. Short‑lived, single‑purpose credentials protect each operation, and admins can enforce organization‑wide policies or disable the feature on specific devices.

Use Cases

• •Start a complex debugging session at your desk, then step away and continue reviewing and approving fixes from your phone while on the couch. The local tools and project files remain fully accessible, and you never lose context.
• •Kick off a long‑running test suite before leaving the office. Receive a push notification when it completes, check the results from a tablet, and instruct Claude to fix failures—all without returning to your machine.
• •Run a server‑mode instance on a team build server with `--spawn=worktree`. Multiple developers can connect from their browsers to trigger builds, review logs, or deploy hotfixes, each in an isolated workspace.
• •Use the VS Code extension’s `/remote-control` command to start a session, close your laptop, and continue the coding conversation from the browser on another computer. The banner keeps you informed of connection status.
• •Set up an automated pipeline where external events (CI failures, Slack messages) trigger Claude to start a remote‑controlled task. You monitor the session from your phone and intervene only when needed, reducing context switches.

Who is this for?

Professional developers and teams who use Claude Code for local coding workflows. Ideal for individuals on Pro or Max plans who need mobile flexibility, and for Team and Enterprise organizations that want to enable remote access while maintaining control via admin policies. Users must be comfortable with CLI tools and optionally use the VS Code extension. The solution is suited for those who rely on MCP servers, custom scripts, and local environment configurations that cannot be moved to the cloud. It is not for casual web‑only users but rather for engineers who want to extend their existing terminal‑based Claude Code sessions to mobile devices and alternate workstations without sacrificing the power of their local toolchain.