What
Resuming a transcript whose remote-control session is still served by a running local process no longer silently conflicts. By default the bridge declines and tells you that running /remote-control here moves it; enabling remote control explicitly takes the session over.
Details
- The decline is logged as
restored_pointer_held_locally; the takeover recordstengu_bridge_restored_pointer_takeover. - A host-directed target re-checks the logged-in owner immediately before connecting and fails with
host_target_owner_recheck_failedif it no longer matches. - Disabling remote control now releases the session record with
keepRecordinstead of deleting it, and the v2 transport close event carriesrecovery_in_flight. - All of this still sits behind the existing
allow_remote_controlpermission check.
Evidence
tengu_bridge_restored_pointer_takeover
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…