CHAPTERS
- 0:04 – 0:35
Remote Control solves “continue Claude Code from anywhere”
The video opens with the common problem of starting a Claude Code session on a desktop and wanting to resume it later from another location. Remote Control is introduced as the feature that lets you connect to that same running session from web or mobile.
- •Common workflow issue: leaving a session running at your desk
- •Remote Control enables continuing the same session remotely
- •Works via Claude Code Web or the Claude mobile app
- •Humorous note about texting so much from mobile
- 0:35 – 1:05
Start a new remote-enabled session from your project directory
You launch Remote Control from the terminal in your project directory. Claude then provides a URL for Claude Code Web, and optionally a QR code for quick phone access.
- •Run Claude Remote Control in the project directory
- •A new session starts and prints a connection URL
- •Press space bar to display a QR code
- •Scan QR to open in mobile browser or Claude app
- •Remote device can view the in-progress session
- 1:05 – 1:15
Hand off an existing session with /remotecontrol
If you’re already inside a Claude Code session, you can enable/inspect Remote Control via a slash command. This reveals the connection URL so you can transition to another device without restarting.
- •Use /remotecontrol within an active session
- •URL is displayed for remote access
- •Enables “handoff” to web or mobile without starting over
- 1:15 – 1:25
Account-linked access and what the remote URL means
The video clarifies that the URL is mainly a convenience. Because Claude Code sessions are tied to your Claude account, you can often access from your device without explicitly using the provided link.
- •Remote access is linked to your Claude account
- •URL is provided for convenience
- •Mobile access can work without manually clicking the URL
- 1:25 – 1:35
Same Claude Code experience—tools, MCP, configs, filesystem
Once connected remotely, the experience mirrors what you get locally in Claude Code. You keep access to the same toolchain and environment because the session is still running on your machine.
- •Remote session exposes the same Claude Code UI/UX
- •Access to tools and MCP servers persists
- •Configurations carry over
- •Full file system access as in the desktop session
- 1:35 – 1:50
Nothing moves to the cloud; real-time sync across devices
The session continues to execute on your local machine, not in the cloud. Inputs and outputs stay synchronized across devices, updating in real time between mobile/web and the terminal.
- •Compute/runtime remains on your machine
- •No project state is migrated to the cloud
- •Conversation stays synced across devices
- •Typing on mobile updates the terminal live
- 1:50 – 2:06
Default prompting vs always-on Remote Control via /config
By default you opt in to Remote Control per session. You can change configuration to enable Remote Control automatically for all sessions, removing the need to turn it on each time.
- •Remote Control is opt-in each session by default
- •You can enable it globally in /config
- •Avoids having to explicitly enable every time
- 2:06
Spawn mode: create new Claude Code sessions remotely
Remote Control includes a spawn mode for starting new sessions from your remote device. This allows creating multiple instances while you’re on web or mobile, selecting which environment/device to run on.
- •Spawn mode lets you create new sessions remotely
- •Run Claude Remote Control, then connect via web/mobile
- •Use the environment button to select your device/session
- •Spawn multiple Claude Code instances
Availability, plans, and rollout status
The video notes current plan availability and rollout timing. As presented, it’s available to Max, Team, and Enterprise users, with rollout underway to Pro and Max plan users.
- •As of the video: available to Max, Team, and Enterprise users
- •Rollout mentioned for Pro and Max plan users
- •Remote Control enables resuming desk-started sessions from anywhere
