You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When managing multiple Claude Code sessions from a mobile device (iPhone via claude.ai/code), the workflow is:
Connect to Session A via remote control
From Session A, spawn a new Terminal tab with a new Claude session
Connect to the new session via remote control
This workflow is currently impossible because the spawned session cannot have remote control enabled programmatically. You must have physical access to the Mac to type /remote-control in the new session.
Requested Feature
Add a --remote-control CLI flag:
claude --remote-control
This would start the session with remote control already enabled, printing the connection URL to stdout immediately. This allows:
Spawning remote-controllable sessions from scripts
Spawning remote-controllable sessions from other remote-controlled sessions
Fully remote management of multiple parallel Claude sessions
Workarounds Attempted
claude --remote-control — flag does not exist
Shell function wrapping claude — strips arguments, but even command claude --remote-control doesn't work since the flag doesn't exist
Summary
There is currently no way to start a Claude Code session with remote control enabled from the CLI. The only options are:
/remote-controlslash command inside a running session (requires interactive input)/config→ "Enable Remote Control for all sessions" toggle (affected by bug "Enable Remote Control for all sessions" resets to false despite persisted config #29929 where it resets to false)Use Case
When managing multiple Claude Code sessions from a mobile device (iPhone via claude.ai/code), the workflow is:
This workflow is currently impossible because the spawned session cannot have remote control enabled programmatically. You must have physical access to the Mac to type
/remote-controlin the new session.Requested Feature
Add a
--remote-controlCLI flag:This would start the session with remote control already enabled, printing the connection URL to stdout immediately. This allows:
Workarounds Attempted
claude --remote-control— flag does not existclaude— strips arguments, but evencommand claude --remote-controldoesn't work since the flag doesn't exist/configtoggle — resets to false (bug "Enable Remote Control for all sessions" resets to false despite persisted config #29929)Related Issues
🤖 Generated with Claude Code