Remote Control: disconnect crashes (session_url undefined) → session accumulates → new connections fail (Session creation failed / Remote credentials fetch failed), one session stuck even after re-auth

Summary

Remote Control has been stuck for one specific session (repo: kks-kitchen) since this morning. Multiple other sessions on the same Desktop instance connect to Remote Control successfully; this one specific session consistently fails, and the failure mode changed over the course of troubleshooting — suggesting several distinct bugs are compounding.

• Claude Code Desktop: 1.21459.0 (native, updated automatically today via auto-updater; previous version 1.20186.1)
• CCD bundled version: 2.1.209
• Platform: win32-x64
• Plan: Max

Timeline / history

1. Yesterday and earlier today, disconnect started failing app-wide. Every attempt to toggle Remote Control off for any session failed with:

``
Failed to toggle remote control for local_XXXX: Cannot read properties of undefined (reading 'session_url')
``
Success rate for disconnect across the whole session log for the day: 0 successful disconnects, out of ~10+ attempts across several different local sessions.

1. Because disconnects never completed, successfully-connected remote sessions accumulated without ever being released. By this morning there were 7 sessions in this state (2 from yesterday, 5 from today), spanning repos kks-kitchen / navideck-Sloop / DevBerth / navideck.

1. New connection attempts started failing with a different error:

``
[remote-control] bridge_state: failed — Session creation failed — see debug log
`
This matches the pattern of a session-limit / accumulation issue: the last successful Remote control enabled was at 07:48:39, and every attempt after 07:49:04 failed with "Session creation failed" (checked via main.log`, timestamps below).

1. Checked claude auth status via the bundled CLI (C:\Users\<user>\AppData\Roaming\Claude\claude-code\2.1.209\claude.exe auth status) — it reported "loggedIn": false", i.e. the bundled CLI/bridge auth was not logged in, despite the Desktop app itself clearly being authenticated (chat, other features work fine).

1. Ran claude auth login via the bundled CLI → completed the OAuth flow in browser → auth status now reports loggedIn: true (authMethod: claude.ai, correct org/email/plan).

1. After re-login, most sessions could connect to Remote Control cleanly (fresh workers picked up the new auth). The kks-kitchen session specifically could not. Its toggle attempts now fail with a third, different error:

``
[remote-control] bridge_state: failed — Remote credentials fetch failed — see debug log
``

1. Tried closing the kks-kitchen session and reopening it from Recents (to force a fresh local worker) — same "Remote credentials fetch failed" error persists after reopening, even with the freshly re-authenticated CLI session.

1. A second affected session (DevBerth) hit the same "Remote credentials fetch failed" error at first, but has since connected successfully after being reopened — so this is not 100% deterministic per-repo, but kks-kitchen has not recovered across 3+ attempts.

Relevant log lines (%APPDATA%\Claude\logs\main.log)

2026-07-17 07:48:14 [info] Enabling remote control for session local_0a3bb565-361e-4ce5-b544-73564c5ee383
2026-07-17 07:48:17 [info] [remote-control] bridge_state: ready
2026-07-17 07:48:17 [info] Remote control enabled: https://claude.ai/code/session_01RbmxcS7FHDLDjoNtofxH1R
...
2026-07-17 08:50:24 [info] Enabling remote control for session local_d6762c1d-...
2026-07-17 08:50:26 [info] [remote-control] bridge_state: failed — Session creation failed — see debug log
2026-07-17 08:50:26 [error] Failed to toggle remote control for local_d6762c1d-...: Session creation failed — see debug log
...
[after claude auth login]
2026-07-17 10:25:12 [info] Enabling remote control for session local_9a2a189f-...
2026-07-17 10:25:13 [info] [remote-control] bridge_state: ready
2026-07-17 10:25:13 [info] Remote control enabled: https://claude.ai/code/session_01K3Vr41kpmefWDMcfgwjXhX
2026-07-17 10:25:33 [error] Failed to toggle remote control for local_0a3bb565-361e-4ce5-b544-73564c5ee383: Cannot read properties of undefined (reading 'session_url')
2026-07-17 10:26:27 [info] Enabling remote control for session local_13dcc31f-63ff-4772-94f1-fd59e3422af4
2026-07-17 10:26:31 [info] [remote-control] bridge_state: failed — Remote credentials fetch failed — see debug log
[after reopening the kks-kitchen session from Recents]
2026-07-17 10:42:40 [info] Enabling remote control for session local_13dcc31f-63ff-4772-94f1-fd59e3422af4
2026-07-17 10:43:00 [info] Enabling remote control for session local_0a3bb565-361e-4ce5-b544-73564c5ee383
2026-07-17 10:43:04 [error] Failed to toggle remote control for local_0a3bb565-361e-4ce5-b544-73564c5ee383: Remote credentials fetch failed — see debug log

Current state (unresolved)

• kks-kitchen session: still cannot connect to Remote Control. Latest error: Remote credentials fetch failed. Persists across session close/reopen and across a full CLI re-login.
• Other sessions on the same Desktop instance connect fine as of the latest attempts.
• No file under %USERPROFILE%\.claude\debug\ was found despite the error referencing "see debug log" (the folder exists but is empty) — see also #57712-style debug-log-path confusion; unclear where CCD's actual bridge debug output is meant to go on Windows.

What I'd like

1. A way to fully reset/clear a single session's Remote Control / bridge state without losing the session's conversation history (short of fully deleting it), since close+reopen did not resolve this.
2. The disconnect-time crash (Cannot read properties of undefined (reading 'session_url')) fixed — this is the root cause that let unreleased sessions accumulate and triggered the whole cascade.
3. Clarification on where "see debug log" actually points on Windows for 1.21459.0 / CCD 2.1.209 — the referenced debug log could not be located locally, which blocked further self-diagnosis.

Steps to reproduce (best guess, not fully deterministic)

1. Have several Remote Control sessions connected simultaneously.
2. Attempt to disconnect any of them via the toggle (hangs / errors with session_url undefined; connection is never actually released server-side).
3. Repeat until new session creation starts failing (Session creation failed).
4. Re-authenticate the bundled CLI (claude auth login).
5. Retry connecting the affected sessions — most recover, but at least one repo-specific session may remain stuck on Remote credentials fetch failed even after reopening.