{"version":"2.1.227","anchor":"sessions-resumed-under-a-different-account-start-clean","canonical_anchor":"sessions-resumed-under-a-different-account-start-clean","heading":"Sessions resumed under a different account start clean","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/sessions-resumed-under-a-different-account-start-clean","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Sessions resumed under a different account start clean\n\nA background session left by another account is dropped rather than reattached under yours.\n\n**What**\n\nIf a background session was left by one account and Claude Code starts under different credentials, the old session is dropped and a fresh one started with history upload suppressed, rather than being reattached to the wrong account.\n\n**Details**\n\n- Applies when the stored owner account does not match the current one, and when the stored identity cannot be read at all.\n- In the mode that must reattach or fail, this raises a terminal error instead of minting a new session.\n- Outcomes are counted under `rc_cross_account_suppression` with reasons including `torn_entry_pair` and `identity_unreadable`.\n\n**Evidence**\n\n`rc_cross_account_suppression`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}