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.229 Home All releases olderv2.1.228 v2.1.231newer
Claude Code v2.1.229

Teleporting a session to the cloud now stops the local remote bridge from reviving it

You'll notice
Useful3 Signal2
Remote Control

After you send a session to the cloud, your terminal stops trying to reconnect to it.

What

Once a session has been sent to the cloud, the local remote-control bridge no longer tries to reattach to it, re-mint its credentials or re-poll for recovery. Each of those paths now bails out early reporting "Session teleported to cloud" rather than reconnecting to a session that has moved.

Details
  • Teleported session ids are held in a bounded set, so very old ids eventually age out.
  • Reattach is either suppressed or fails terminally depending on the path.
  • New counters: bridge_repl_v2_revive_reattach_teleported and bridge_repl_v2_remint_loop_teleported.
Evidence

[remote-bridge] Reattach suppressed for teleported session

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.229 →