Persistent always-on Remote Control option for desktop app

Summary

The CLI supports remoteControlAtStartup: true in ~/.claude.json to auto-enable Remote Control for every session. The desktop app (v1.2773.0.0 with claude-code 2.1.92 bundled) ignores this setting — it uses a separate per-session remoteControlEnabled runtime state that defaults to false and must be manually toggled for each session.

Use case

I use Claude Code primarily from my phone via the Claude mobile app's Remote Control feature. Having to walk to my PC and manually enable Remote Control for each new desktop session defeats the purpose of mobile access.

Evidence from code

• ~/.claude.json has remoteControlAtStartup (read by Fd() in claude-code backend 2.1.92)
• Desktop app (1.2773.0.0) has separate remoteControlEnabled runtime state: e.remoteControlEnabled=!1 (defaults false, must be toggled per session)
• The two are not wired together — setting the CLI flag has no effect on desktop app behavior

Requested fix

Have the desktop app honor remoteControlAtStartup from ~/.claude.json, or add an equivalent persistent toggle in the desktop app UI (currently /config is CLI-only).

Environment

• Windows 11 25H2
• Claude Code Desktop 1.2773.0.0 (claude-code 2.1.92 bundled)