Desktop: Remote Control links are lost on account switch and idle chats cannot be relinked

Summary

On Claude Desktop (Code tab), every chat's Remote Control link belongs to the claude.ai account it was created under. After signing Desktop out of account A and into account B on the same Mac, the Claude mobile app (now on account B) lists none of the existing Desktop chats. Desktop only creates a new link for a chat when that chat runs a turn; idle chats cannot be relinked at all. A user with several accounts (Max plan rotation) therefore loses their whole phone list at every switch and has to send a throwaway message into every chat to get it back.

Environment

• Claude Desktop 2.2553.1, Claude Code CLI 2.1.275, macOS 26.6 (Darwin 25.6.0)
• Two events, 21 Sep 2026 09:42 and 22 Sep 2026 21:18 (Bangkok), both reproduced the same way

Steps to reproduce

1. In Desktop, have several Code-tab chats with Remote Control on; confirm they show in the mobile app.
2. Bottom-left account menu → Log out → sign in with a second account on the same machine.
3. Open the mobile app on the second account: no Desktop chat is listed.
4. Try to switch Remote Control on for an idle chat (toolbar switch, or the session-management tool set_remote_control). Refused: "Remote Control requires an active session. Send a message first." main.log: Cannot toggle remote control for local_<id>: no active query.
5. Opening the chat in the sidebar does not help (main.log: "Warming session", toggle still refused).
6. Send any message into the chat: main.log logs "Enabling remote control for session local_<id>", a new entry appears in the chat record's bridgeSessionIds, and the chat shows on the phone.

Log excerpt (22 Sep 2026)

21:17:58 [info] [account] Login-state transition (loggedOut: false → true, uuid: <A> → <none>), clearing oauth cache
21:17:58 [info] [sessions-bridge] identity reevaluate: <org>:<A> → <none>
21:17:58 [info] [sessions-bridge] Disposing...
21:18:41 [info] [account] Login-state transition (loggedOut: true → false, uuid: <A> → <B>), clearing oauth cache
21:30:06 [warn] Cannot toggle remote control for local_5752bc57-...: no active query
21:31:21 [info] Enabling remote control for session local_62bac9fc-...   (only after a message was sent into it)

Expected

Either of these would fix it:

• On account change, Desktop re-registers Remote Control for every chat that had it, under the newly signed-in account (the chat records already carry remoteControlAutoEligible: true).
• Or the Remote Control switch works on an idle chat, so a chat can be relinked without spending a model turn in it.

Related smaller issue

After the 21 Sep switch, three relinked chats appeared in the mobile app under generated names ("emanuels-macbook-pro-5-local-<word>") while the local chat record held the right title. Switching Remote Control off and on again for that chat produced a fresh link with the correct title; the wrongly named entry stayed on the phone as a dead item.

Workaround in use

For each chat that was linked before the switch: switch the chat's model to Haiku, send "reply ok, run no tools", wait for "Enabling remote control" in main.log, switch the model back. Ten chats take about a minute in batches of five, but each wake re-reads the chat's whole context.