Remote Control session list shows connection kind but never which machine a session runs on
Setup
Three Windows 11 machines signed in to one account, Remote Control enabled, and the same repository checked out on more than one of them. Claude Code 2.1.252.
Observed
From any one machine, sessions belonging to the other machines are listed. Each row shows a session name and Remote Control as the kind. Nothing on the row indicates which physical machine the session is actually running on. With six peer sessions listed, all six carried the identical Remote Control label and no host.
Why it matters
When the same project is checked out on several machines, session names collide — and machine identity is load-bearing: scheduled jobs, local credentials, and machine-specific setup all differ per box. There is currently no way to tell which machine a listed session belongs to, so picking the right one is guesswork.
Related detail (this rules out the obvious workaround)
Renaming a session does not propagate to how other machines display it. A session renamed on machine A still appears under its originally-registered name on machine B. Statuses in that same list (running / idle / offline) do update live, so the list is clearly connected — only the name appears to be fixed at registration time. A session that had no title when it registered is shown to its peers as a handle derived from its folder name.
So a "put the machine name in the title" convention cannot rescue a session that is already running.
Also
The machine-local session list excludes these peers entirely, so there is no second place to look up the host.
Ask
Show the host — or a user-settable machine label — on each row of the peer/session list. And/or let a title change propagate to peers.