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.234 Home All releases olderv2.1.233 v2.1.235newer
Claude Code v2.1.234

Remote Control stops a live session when the signed-in account changes

You'll notice
Useful3 Signal3
Remote Control

A live remote session now shuts down if you sign into a different account mid-session.

Feature flag
tengu_bridge_owner_pinned_end Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.234: off

tengu_bridge_recover_stale_epoch Not enough to say

Nothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.

This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.234: not a boolean we can read

Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you

What

A remote-control bridge session now pins the credential the server accepted at the start, and if the local signed-in account changes while the session is live it shuts the session down instead of carrying on under the new identity. Credential work in flight, including re-minting, refreshing and recovery, stops at the same point rather than running against the old owner. The whole behaviour sits behind the tengu_bridge_owner_pinned_end gate, which falls back to on.

Details
  • On detecting the change the session logs "Signed-in account changed under … — stopping", sends an account_changed frame to the connected peer, and stops recovery and token-refresh work.
  • Subscription and unsubscription calls refuse with { ok: !1, reason: "owner_changed" }, and token fetches short-circuit.
  • Early-exit checks named owner_changed_refresh and owner_changed_recovery cover the credential paths, and the session settles into a terminal state named owner_changed.
  • Credential fetches can use a token pinned to the original owner, recorded in telemetry as source: "pinned_owner".
  • Archiving is skipped with its own outcome, skipped_owner_changed, rather than falling into the generic suppression path, and message delivery treats the condition as terminal and does not retry.
  • Reconnect returns suppressed_owner_changed and closes the connection instead of rebuilding the transport.
  • New telemetry tengu_bridge_owner_changed carries the site, the archive status and whether the episode was already dead; teardown telemetry gained an archive_credential field; the diagnostics event is bridge_repl_v2_owner_changed.
  • Per-attempt send-time bookkeeping was dropped from these paths, and the older tengu_bridge_recover_stale_epoch gate was deleted in the same rework.
Evidence

bridge_repl_archive_suppressed_owner_changed, tengu_bridge_owner_changed, bridge_repl_v2_owner_changed, suppressed_owner_changed

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