Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Remote control can take over a session another process still holds

You'll notice
Useful3 Signal3
Remote Control

Resuming a session another process still holds now tells you to run /remote-control to take it over.

/remote-control
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 records tengu_bridge_restored_pointer_takeover.
  • A host-directed target re-checks the logged-in owner immediately before connecting and fails with host_target_owner_recheck_failed if it no longer matches.
  • Disabling remote control now releases the session record with keepRecord instead of deleting it, and the v2 transport close event carries recovery_in_flight.
  • All of this still sits behind the existing allow_remote_control permission check.
Evidence

tengu_bridge_restored_pointer_takeover

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.232 →