remoteControlAtStartup: true not honored by VSCode extension on new sessions

Description

remoteControlAtStartup: true (the setting written by /config -> "Enable Remote Control for all sessions") is not honored by the VSCode extension when new sessions start. New sessions do not appear on remote devices unless /remote-control is invoked manually in each one.

The setting appears to work as documented for CLI interactive sessions, but the VSCode extension still requires manual invocation per session. The docs do not call out any CLI-vs-extension distinction for this setting.

Steps to Reproduce

1. In the VSCode extension, run /config and set "Enable Remote Control for all sessions" to true (confirmed written as "remoteControlAtStartup": true in ~/.claude/settings.json).
2. Fully restart VSCode / the extension.
3. Start a new session.

Expected Behavior

The new session auto-enables Remote Control at startup and appears on the remote device (mobile app / claude.ai/code) without any manual action.

Actual Behavior

New sessions do not appear on the remote device. They only appear after manually typing /remote-control in each session.

Notes / What Was Ruled Out

• "remoteControlAtStartup": true is present in the global ~/.claude/settings.json.
• Manually invoking /remote-control connects instantly every time - so account/login, network, and any org-level Remote Control gate are all fine.
• The behavior persists across a full app restart.

Environment

• Claude Code VSCode extension: anthropic.claude-code-2.1.160-win32-x64
• OS: Windows 11 Business, build 10.0.26100
• Setting location: global ~/.claude/settings.json