What
When another Claude Code on the same machine already has Remote Control for a conversation, you now get a message saying so and pointing at /remote-control to move it to the current terminal.
Details
- The remote control request gained two fields: one naming a session to reattach to, and one asking that the session not be archived when it exits.
- The receiving side reads those as a reattach session id and a never-archive flag.
Evidence
already has Remote Control for this conversation · run /remote-control to move it to this terminal
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…