Add remoteControlEnabled setting to auto-start /remote-control on session start

Summary

There is no settings.json option to auto-enable /remote-control on session start. Users who rely on remote control every session must manually type /remote-control each time. There should be a remoteControlEnabled: true setting (mirroring the existing voiceEnabled pattern) that auto-starts the remote control server on session initialization.

Current Behavior

• /remote-control must be manually typed every session
• SessionStart hooks can only run shell commands, not invoke built-in slash commands
• No settings.json property exists to auto-enable this feature

Expected Behavior

{
  "remoteControlEnabled": true
}

Adding this to ~/.claude/settings.json should auto-start the remote control server on every session, just like voiceEnabled: true auto-enables voice mode.

Use Case

Users who control Claude Code from a separate device (phone, tablet, another screen) need remote control active every session. Having to walk to the terminal and type /remote-control each time defeats the purpose of the feature.

Environment

• OS: Windows 11 Pro 10.0.26200
• Claude Code: latest (CLI)