remoteControlAtStartup not applied to sessions restored after Desktop app restart

Title

remoteControlAtStartup not applied to sessions restored after Desktop app restart

Body

Setup

• Desktop app (Claude Code inside claude.ai desktop app)
• ~/.claude/settings.json has "remoteControlAtStartup": true

Observed behavior

• Brand-new sessions started after setting this option are automatically connected to Remote Control (visible in the iOS/Android app's "Code" tab) — this works as documented.
• However, when the Desktop app itself is restarted and previously-open conversation windows are restored/resumed, those restored sessions are not automatically Remote-Control-enabled, even though remoteControlAtStartup is still true in settings.
• Each restored session requires manually running /remote-control (or /rc) again to reconnect it.

Expected behavior

• Since remoteControlAtStartup is meant to auto-enable Remote Control at session start, sessions restored on Desktop app relaunch (which are, from the process's perspective, freshly started) would ideally also pick up this setting automatically — or there would be a documented way to batch re-enable it for all currently-open sessions without doing it one window at a time.

Impact

• Users with several open conversation windows have to manually re-run /remote-control in each one, every single time the Desktop app restarts (e.g. after an update). This defeats much of the convenience of the remoteControlAtStartup setting.

Ask

• Either make restored/resumed sessions on Desktop app relaunch honor remoteControlAtStartup, or provide a command/flag to re-enable Remote Control for all currently-open sessions at once.