Add --remote-control flag to interactive sessions

Resolved 💬 3 comments Opened Apr 16, 2026 by pih-dev Closed Apr 16, 2026

Feature Request

Add a CLI flag (e.g., --remote-control <name>) to the main claude command that auto-starts Remote Control when launching an interactive session.

Use Case

I run 7 projects, each with its own Windows Terminal tab that auto-launches Claude Code with --dangerously-skip-permissions. Every time I restart terminals, I have to manually type /rc "ProjectName" in each session to connect Remote Control.

Being able to pass claude --dangerously-skip-permissions --remote-control "CCHealth" would eliminate this repetitive step across all projects.

Current Behavior

  • claude remote-control --name "X" exists but starts a bridge server, not an interactive session
  • --remote-control-session-name-prefix only sets a prefix for auto-generated names
  • The only way to connect RC in an interactive session is typing /rc "Name" or /remote-control "Name" after startup

Desired Behavior

claude --remote-control "MyProject" --dangerously-skip-permissions

This would launch an interactive session AND auto-connect Remote Control with the given name, combining both in a single command.

Environment

  • Claude Code 2.1.110
  • Windows 11, Windows Terminal with 7 project tabs
  • Each tab auto-launches claude in its project directory

🤖 Generated with Claude Code

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗