[BUG] [Desktop / Windows] Remote Control does not reconnect after app launch until you type in the session locally

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Environment

• OS: Windows 10 Pro (build 19045), laptop
• Claude Desktop (MSIX, installed from claude.ai/download): 2.9939.2.0
• Embedded Claude Code: 2.1.281
• Code tab setting "Connect new sessions to Remote Control": On
• Claude Desktop launches automatically at Windows login (startup task enabled)

What happens

I use a local Code tab session with Remote Control turned on, so I can follow and steer it from my phone when I'm away from the laptop.

After the laptop is shut down and turned on again:

1. Claude Desktop starts automatically at login.
2. The session still shows Remote Control as enabled (the switch is on).
3. From my phone, I cannot connect to the session. It is not reachable.
4. As soon as I type any message into the session on the laptop, Remote Control connects and the phone can reach it.

Checked via the app's session info right after launch: the session is not running (isRunning: false) and Remote Control is not active (remoteControlActive: false), even though Remote Control is switched on for it. After I type one message locally, it becomes isRunning: true, remoteControlActive: true, remoteControlState: "on".

Fully quitting and reopening the app, and reinstalling the latest version from claude.ai/download, both give the same result.

Expected

When Claude Desktop starts, sessions that have Remote Control switched on should reconnect to Remote Control automatically, without anyone having to interact with the session on the computer. The purpose of Remote Control is to reach the session when I'm not at the computer.

Actual

Remote Control only connects after the session is used locally once, so it doesn't work in the situation it's meant for (laptop restarted, user away).

Workaround

Type something into the session on the computer after every restart, which defeats the purpose.

What Should Happen?

When Claude Desktop starts, sessions that have Remote Control switched on should reconnect to Remote Control automatically, without anyone typing into the session on the computer. Remote Control is meant for reaching the session when I'm away from the computer.

Error Messages/Logs

Steps to Reproduce

1. In Claude Desktop (Windows), open a Code tab session and turn Remote Control on for it. Confirm it can be reached from the phone.
2. Shut down the computer.
3. Turn the computer on and log in. Claude Desktop starts automatically.
4. Without touching the session on the computer, try to open it from the phone via Remote Control: it is not reachable.
5. On the computer, type any message into the session.
6. Try again from the phone: it now connects.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.281 (Claude Code, embedded in Claude Desktop 2.9939.2.0)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This is the Claude Desktop app's Code tab, not the terminal CLI. Windows 10 Pro build 19045, laptop.