What
When a remote session ends because another device claimed it, the disconnect notice no longer suggests running /remote-control to reconnect. That advice was pointing you back at a session that had legitimately moved elsewhere.
Details
- The new end reason is raised when the transport closes with a superseded code, or when another connection wins the race to own the session.
Evidence
another connection took over this session while it was being restored — this device is standing down
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle/remote-control
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up /remote-control, on Claude Code changelog.
* Fixed `/remote-control` and other claude.ai-gated commands to suggest `/login` when signed out instead of showing a Claude for Enterprise migration messagechangelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /remote-control, on Claude Code changelog.
Anthropic's release notes agree
Remote Control: resuming a conversation no longer silently takes Remote Control away from another Claude Code on the same machine that still…