Source Intelligence

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 stops telling you to reconnect a session another device took over

You'll notice
Useful3 Signal2
Remote Control

When another device takes over your remote session, you're no longer told to reconnect to it.

/remote-control
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.

See this entry in the whole of v2.1.232 →