{"version":"2.1.227","anchor":"session-history-is-withheld-when-the-signed-in-account-chang","canonical_anchor":"session-history-is-withheld-when-the-signed-in-account-chang","heading":"Session history is withheld when the signed-in account changed","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/session-history-is-withheld-when-the-signed-in-account-chang","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Session history is withheld when the signed-in account changed\n\nResuming a session under a different account starts fresh instead of replaying the old history.\n\n**What**\n\nWhen Claude reattaches to a session that was started earlier or handed over from another process, it now compares the account and organization recorded on that session against whoever is signed in now. On a mismatch it starts a fresh session instead and withholds the earlier history rather than replaying it under the new account.\n\n**Details**\n\n- The handoff carries the previous owner identity in new environment variables including `CLAUDE_BRIDGE_REATTACH_OWNER_ACCT`.\n- A suppression record is written into the transcript and `rc_cross_account_suppression` is emitted, with `torn_entry_pair` and `scan_budget_exhausted` variants for partially written or too-large transcripts.\n\n**Evidence**\n\n`CLAUDE_BRIDGE_REATTACH_OWNER_ACCT`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}