/config remoteControl=true confirmation is ambiguous about when it takes effect

What happened

Running /config remoteControl=true prints:

Set Enable Remote Control for all sessions to true

The phrase "for all sessions" reads as though the change applied to sessions that are already running, including the one you typed it in. It doesn't.

Actual behaviour

The /config key remoteControl writes the settings key remoteControlAtStartup, described in the settings schema as "Start Remote Control bridge automatically each session." It is evaluated at session start only:

• In the VS Code extension there is exactly one auto-enable call site, inside initializationResult().then(...), gated on the freshly-spawned channel's remoteControlState.status === "disconnected".
• Nothing re-evaluates it for a channel that is already up, so an existing session never retroactively connects.

The result is that after running the command, the user reasonably expects Remote Control to be on, and it silently isn't — until they start a new session or run /rc.

Suggested wording

Set Enable Remote Control for all sessions to true · applies to new sessions — run /rc to enable it here

The same ambiguity applies to the setting's label ("Enable Remote Control for all sessions") in the interactive /config list under Connections.

Environment

• Claude Code 2.1.247 (native build, linux-x64)
• VS Code extension anthropic.claude-code-2.1.247-linux-x64
• Fedora Linux 44 on WSL2