Enable remote control by default toggle in Claude Desktop does not apply to new Claude Code sessions

[gborghi]

Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code CLI: 2.1.143
• Claude Desktop: latest (auto-updates channel)

Steps to reproduce

1. In Claude Desktop → Settings, enable "Enable remote control by default — Automatically connect new local sessions to Remote Control so you can continue them from the CLI or claude.ai/code".
2. Fully quit and reopen Claude Desktop.
3. Open a new Claude Code session inside Claude Desktop.
4. Visit claude.ai/code.

Expected

The new session appears in the Remote Control session list and can be resumed from claude.ai/code.

Actual

The session does not appear and is not remote controlled, even after a full Claude Desktop restart and starting a fresh session.

Notes

• The "Enable remote control by default" toggle is exposed only in Claude Desktop's Settings, not on claude.ai/code.
• The setting is not reflected in %USERPROFILE%\.claude\settings.json (only autoUpdatesChannel and enabledPlugins are present), so the toggle state is presumably stored in Desktop's own config.

[github-actions]

Found 3 possible duplicate issues:

1. Desktop Code tab doesn't honor remoteControlAtStartup from ~/.claude/settings.json #50059
2. remoteControlAtStartup: true in settings.json does not auto-enable remote control on new sessions #54527
3. Persistent always-on Remote Control option for desktop app #48949

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[github-actions]

This issue has been automatically closed as a duplicate of #50059.

If this is incorrect, please re-open this issue or create a new one.

🤖 Generated with Claude Code

[ETechSol]

Confirming on Claude desktop 1.10628.0.0 (Windows, MSIX/Store install).

"Settings → Claude Code → Enable remote control by default" is ON.
After restarting the app (or rebooting the machine), every project shows
"Turn on Remote Control" — i.e. remote control is OFF and must be enabled
manually per project. The default toggle does not apply on startup.

Expected: with the toggle ON, remote control should auto-enable for
projects when the app launches, so a 24/7 setup reconnects without
manual clicks after reboot.

Use case: machine runs unattended (auto-login + auto-restart). Having to
manually re-enable remote control per project after every reboot defeats
the unattended setup.

[Rak542]

Feature request: make Remote Control persist across restarts in the desktop app.

I keep several long-running sessions with Remote Control turned on so I can pick
them up from my phone when I'm away. The problem: every time my PC restarts, or
if the desktop app closes and reopens, all those sessions come back with Remote
Control OFF. I have to open each session and click the computer icon at the top
to turn it back on, one by one.

Please add a way to keep Remote Control ON for chosen sessions so it
re-activates automatically when the app reopens — ideally a per-session
"always keep remote control on" setting, or a global setting that actually
re-arms existing/resumed sessions on launch. Right now the only auto-on-boot
option is the CLI --remote-control flag, which can't run while the same session
is open in the desktop app.