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

Bridge account pinning distinguishes a real account switch from a stale identity file

Under the hood
Useful2 Signal3
Remote Control

The bridge now checks with the server before ending a session, so a stale identity file no longer kills it.

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

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

Before tearing a remote session down for an account change, the bridge cross-checks the local identity file against which account the server says the credential belongs to. A genuine switch ends the episode and archives using the original owner's credential; a disagreement where the server still attributes the credential to the owner just re-baselines and keeps going. Gated on tengu_bridge_owner_pinned_end, fallback on.

Details
  • The session pins both the account and organization it started under.
  • The re-baseline case is logged rather than silent.
Evidence

[bridge:owner-pin] identity file names another account but the server attributes the credential to the owner — re-baselining

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 →