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.242 Home All releases olderv2.1.241 v2.1.243newer
Claude Code v2.1.242

The remote-control bridge recovers when the server forgets it

You'll notice
Useful3 Signal3
Remote Control

Remote control re-registers and reattaches your sessions if the server forgets this machine.

What

If the server replies 404 to the bridge's work poll, meaning it no longer knows this machine, the bridge now re-registers itself and resumes instead of shutting down, re-attaching every live session. It is controlled remotely by tengu_glimmering_glade, which is on when the server says nothing.

Details
  • Re-registration asks to reuse the same environment id, up to 3 attempts; if the server hands back a different id, the replacement is deregistered and the bridge gives up.
  • On success it adopts the new environment secret and re-queues each active session.
  • Verbose output shows Environment re-registered; resuming poll. or Re-registration failed; retrying after backoff.
  • New event tengu_bridge_env_reregister with outcomes register_rejected, register_transient, replaced, reregistered, recovered, requeue_dropped, gave_up, plus a bridge_env_reregistered log line.
Evidence

tengu_bridge_env_reregister

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