Remote Control auto-enables on every new tab in VSCode extension, ignoring remoteControl=default setting

Status Open
Reported on v2.1.240
Maintainer reply None cached
Activity 2 comments · opened Aug 24, 2026

Remote Control auto-enables on every new tab in VSCode extension, ignoring remoteControl=default setting

Environment

  • Claude Code VSCode extension (anthropic.claude-code), version 2.1.240 (also reproduced on 2.1.238, 2.1.235, 2.1.233, 2.1.226 per locally cached VSIX history)
  • macOS (Darwin 25.5.0), VSCode
  • Not a git repository / general workspace

Expected behavior
Remote Control should only activate when explicitly invoked (/remote-control, claude --remote-control, or the / menu toggle), per the documented behavior at https://code.claude.com/docs/en/remote-control.md. Setting remoteControl=default via /config should suppress any automatic connection.

Actual behavior
Every new Claude Code tab/session opened in the VSCode extension automatically turns Remote Control on, even after:

  1. Running /config remoteControl=default (confirmed no remoteControlAtStartup/remoteControl override exists in ~/.claude/settings.json or ~/.claude.json prior to this, so the setting was applied cleanly).
  2. Fully restarting VSCode (ruling out a stale in-memory session state).

Root cause (as far as I can tell from local state)
~/.claude.jsoncachedGrowthBookFeatures contains:

"tengu_ide_rc_auto_enable": true

This appears to be a server-controlled experiment/rollout flag that force-enables Remote Control specifically for IDE (VSCode) sessions, and it takes precedence over the user's local remoteControl config — the local setting change had no effect on the behavior.

Supporting evidence: VSCode's extension global state (state.vscdb, key Anthropic.claude-code) contains "rcAutoOnDisclosureImpressions": 1, suggesting there's a one-time disclosure notice tied to this auto-on experiment, separate from the normal manual-invocation flow.

Impact
Remote Control (which exposes the local session to control from another device/browser) is being silently enabled on every new tab without the user opting in per-session, and without the documented user-facing setting being able to override it.

Request

  • Local remoteControl/remoteControlAtStartup config should take precedence over the tengu_ide_rc_auto_enable experiment flag, OR
  • The experiment should not force auto-enable for users who have explicitly set remoteControl=default/false.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗