"Enable Remote Control for all sessions" resets to false despite persisted config

Bug Description

The "Enable Remote Control for all sessions" setting in /config repeatedly resets to false, even though the underlying config file (~/.claude.json) has "remoteControlAtStartup": true.

Every new session starts with Remote Control disabled. The user must manually re-enable it each time via /config.

Steps to Reproduce

1. Open Claude Code
2. Run /config
3. Toggle "Enable Remote Control for all sessions" to true
4. Close the session
5. Start a new Claude Code session
6. Run /config again
7. Observe: "Enable Remote Control for all sessions" is back to false

Expected Behavior

The setting should persist across sessions. Once enabled, Remote Control should remain enabled for all subsequent sessions.

Actual Behavior

The setting resets to false on every new session, despite ~/.claude.json containing:

{
  "remoteControlAtStartup": true
}

There appears to be a desync between the persisted file value (true) and what the /config UI reads at startup (false).

Environment

• Claude Code version: 2.1.63
• OS: macOS 26.3 (Tahoe)
• Install method: native ("installMethod": "native" in ~/.claude.json)
• Auto-updates: disabled ("autoUpdates": false)
• Plan: Claude Max (Opus 4.6)

Additional Context

• The ~/.claude.json file correctly contains "remoteControlAtStartup": true — the value is being written but not read back (or overridden at startup).
• "autoUpdates": false is set, so this is not caused by an auto-update overwriting the file.
• Possibly related to #2095 (settings persistently resetting) and #10764 (settings being bypassed).

Feature Request (if by design)

If the setting intentionally doesn't persist, please consider adding:

• A CLI flag (e.g., claude --remote-control) to start with RC enabled
• Or an environment variable (e.g., CLAUDE_REMOTE_CONTROL=1) for shell profile integration