Add --remote-control CLI flag to start sessions in remote control mode

Feature Request

Problem

There's no way to start a Claude Code session with remote control enabled via a CLI flag. The current options are:

1. claude remote-control — starts a dedicated remote control session (not a normal interactive session with RC added)
2. /rc inside an existing session — requires manual intervention
3. Global config "Enable Remote Control for all sessions" — all or nothing

Use Case

When running multiple Claude Code sessions (e.g., multiple executor instances in a development workflow), only some sessions need remote control. The global config is too broad, and manually typing /rc after each session starts isn't practical — especially for auto-launched sessions (e.g., when context runs out and a new session is spawned automatically with compressed context).

Proposed Solution

Add a --remote-control flag to the claude command:

claude --remote-control

This would start a normal interactive Claude Code session with remote control automatically enabled — combining the normal session experience with remote accessibility.

Why This Matters

• Enables selective remote control per session without the all-or-nothing global config
• Critical for auto-spawned sessions where there's no opportunity to manually type /rc
• Fits naturally alongside existing flags like --verbose, --model, etc.