[BUG] VS Code extension ignores remoteControlAtStartup (still repro on 2.1.185; refile of locked #41036)

Resolved 💬 2 comments Opened Jun 21, 2026 by eatsleepmath Closed Jun 25, 2026

Preflight Checklist

  • [x] I have searched existing issues to make sure this isn't a duplicate
  • [x] This is a single bug report (not bundling multiple bugs)
  • [x] I am using the latest version of Claude Code

What's wrong?

The VS Code extension does not auto-enable Remote Control on session start, even though remoteControlAtStartup: true is set in ~/.claude/settings.json. The setting works correctly in the CLI — claude doctor shows Remote Control ✓ and new CLI sessions auto-connect. In the VS Code extension, every new session starts with Remote Control off and I have to run /remote-control manually each time.

This is a re-file of #41036, which was auto-closed as a duplicate of #29929 and then locked. It is not a duplicate of #29929 — that issue is about the CLI setting resetting/not persisting. Here the setting persists fine and works in the CLI; the bug is that the VS Code extension ignores it at startup. A commenter on #41036 raised the same correction before it was locked.

What should happen?

With remoteControlAtStartup: true, the VS Code extension should auto-enable Remote Control on session start, same as the CLI.

Steps to reproduce

  1. Ensure ~/.claude/settings.json contains "remoteControlAtStartup": true.
  2. Open a new session in the CLI terminal — Remote Control auto-connects (claude doctor → Remote Control ✓). ✅
  3. Open a new session in the VS Code extension — Remote Control does NOT auto-connect. ❌
  4. Running /remote-control manually in VS Code works, so the feature itself is supported — only the auto-enable path is broken in the extension.

Is this a regression?

Still reproduces; not improved since #41036 was filed at 2.1.87.

Claude Code Version

2.1.185

Platform

claude.ai (OAuth subscription)

Operating System

macOS 15.7.3

Terminal/Shell

VS Code extension

Additional Information

Related: #41036 (this exact bug, closed-as-dup-then-locked), #29929 (the CLI persistence bug it was wrongly merged into).

View original on GitHub ↗

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