Remote Control sessions on my Windows PC end before attaching (“Couldn’t start …

What happened
Remote Control sessions on my Windows PC end before attaching (“Couldn’t start in <folder>”)

When a Claude Projects thread starts a Remote Control session on my PC (Claude desktop app, Windows, one registered folder), about 1 in 6 starts fail and the chat shows “Couldn’t start in <folder>”. The desktop app accepts every start; the server ends the session about 0.2 s later, before it attaches. From %LOCALAPPDATA%\Claude\logs\remote-control.log:

admitted (new, nudge poll) session=cse_…
[warn] not attached (session_ended)

The hourly summary shows "refused":0, so the PC does not reject anything: there is no local session limit, folder lock or conflict with other registered folders. It fails even with only one other session running, while at other times two sessions run side by side without problems.

First seen 2026-10-09 around 11:14 UTC. On 2026-10-11 it failed 9 of 56 starts (UTC: 00:34 ×2, 11:02 ×2, 13:48, 15:25 ×2, 15:42 ×2). Retrying about 20 s later usually works on the third try. No settings were changed on the PC.

Expected: the session attaches. Actual: the server reports session_ended immediately after admission.

Environment

• Filed from: Report a problem in Claude Code
• Project ID: chan_01BkG1AR3WMNBPRePU36gjMz