Add remoteControlEnabled setting to settings.json for persistent remote control

Feature Request

Add a remoteControlEnabled (or similar) key to settings.json so that remote control can be enabled persistently across sessions without manual /rc invocation each time.

Current Behavior

• Remote control must be enabled manually each session by typing /rc
• The --rc / --remote-control CLI flag only works in text/CLI mode, not the desktop app
• There is no settings.json key to persist this preference
• /config does not appear to offer this toggle (it auto-corrects to other commands)

Desired Behavior

A setting like:

{
  "remoteControlEnabled": true
}

in ~/.claude/settings.json (user scope) that automatically enables remote control when a session starts — across all launch modes (CLI, desktop app, etc.).

Use Case

Users who rely on remote control for multi-instance workflows (e.g., coordinating between Claude instances via remote triggers, or reaching into sessions from mobile/other devices) currently have to remember to type /rc every single session. This is a small but persistent friction point that a config option would eliminate entirely.

Environment

• Windows 11, Claude Code desktop app (MSIX)
• Also applicable to CLI mode on all platforms