{"version":"2.1.228","anchor":"refreshed-oauth-tokens-no-longer-leave-a-stale-account-cache","canonical_anchor":"refreshed-oauth-tokens-no-longer-leave-a-stale-account-cache","heading":"Refreshed OAuth tokens no longer leave a stale account cached","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/refreshed-oauth-tokens-no-longer-leave-a-stale-account-cache","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Refreshed OAuth tokens no longer leave a stale account cached\n\nAfter a token refresh, requests use your current account rather than the previous one.\n\n**What**\n\nAfter a token refresh, Claude Code clears the cached snapshot of the signed-in account (account id, email, organisation), so requests made after the refresh use the current account rather than the previous one.\n\n**Details**\n\n- Applies after recovering from a 401 using the token on disk, after an SDK token callback refresh, after adopting a newer token written by another Claude Code process, and on login-state reset.\n- Request metadata for the account id now falls back to the stored OAuth account.\n\n**Evidence**\n\n`tengu_oauth_401_recovered_from_disk`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}