Add --remote-control CLI flag to enable remote control at session start

Summary

There is currently no way to start a Claude Code session with remote control enabled from the CLI. The only options are:

1. /remote-control slash command inside a running session (requires interactive input)
2. /config → "Enable Remote Control for all sessions" toggle (affected by bug #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:

1. Connect to Session A via remote control
2. From Session A, spawn a new Terminal tab with a new Claude session
3. 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
• /config toggle — resets to false (bug #29929)
• SessionStart hooks — cannot invoke slash commands
• AppleScript keystroke injection — blocked by macOS security

Related Issues

• #29929 — "Enable Remote Control for all sessions" setting resets to false
• #30495 — "Enable Remote Control for all sessions" option missing from /config

🤖 Generated with Claude Code