{"version":"2.1.234","anchor":"bridge-account-pinning-distinguishes-a-real-account-switch-f","canonical_anchor":"bridge-account-pinning-distinguishes-a-real-account-switch-f","heading":"Bridge account pinning distinguishes a real account switch from a stale identity file","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/bridge-account-pinning-distinguishes-a-real-account-switch-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Bridge account pinning distinguishes a real account switch from a stale identity file\n\nThe bridge now checks with the server before ending a session, so a stale identity file no longer kills it.\n\n**What**\n\nBefore 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.\n\n**Details**\n\n- The session pins both the account and organization it started under.\n- The re-baseline case is logged rather than silent.\n\n**Evidence**\n\n`[bridge:owner-pin] identity file names another account but the server attributes the credential to the owner \u2014 re-baselining`\n\n- Flag `tengu_bridge_owner_pinned_end`: Not enough to say (read for one account on one subscription tier against v2.1.234; this account: no value returned, anonymous baseline: no value returned, compiled default: on)\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}