remoteControlAtStartup is ignored by the VS Code extension

The feature requested in #46317 now partially exists — "remoteControlAtStartup": true
in ~/.claude/settings.json works correctly for terminal CLI sessions — but the
VS Code extension ignores it entirely, so the original problem remains for
extension users: /remote-control must be typed manually every session.

Environment: Claude Code 2.1.216, VS Code extension (native panel), macOS,
claude.ai OAuth login (paid subscription). No managed settings, no
ANTHROPIC_API_KEY/ANTHROPIC_BASE_URL overrides.

Expected: with remoteControlAtStartup: true, every session — including
extension panel sessions — auto-connects remote control, as documented
(https://code.claude.com/docs/en/remote-control.md, which says the VS Code
extension supports this from v2.1.203).

Actual: extension panel sessions never auto-connect; the setting is only
honoured by the terminal CLI.

Why there's no workaround in the extension:

• Hooks can't invoke slash commands, and SessionStart hooks don't fire in the

extension panel (#21736)

• No extension command exists to send a slash command from a keybinding (#29752)
• claudeCode.useTerminal is defined but never read (#38642)

Related prior reports, closed as duplicate/not-planned: #53647, #41036, #54527.

Remote control is most valuable precisely in always-on workflows — needing a
manual incantation per session defeats it. Could the extension read
remoteControlAtStartup at session init, or failing that, expose any hook/
command that can trigger /remote-control?