{"version":"2.1.312","anchor":"sign-in-bearer-tracking-and-handed-out-token-mapping","canonical_anchor":"sign-in-bearer-tracking-and-handed-out-token-mapping","heading":"Sign-in tokens handed out earlier can now be matched to the current one","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/sign-in-bearer-tracking-and-handed-out-token-mapping","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Sign-in tokens handed out earlier can now be matched to the current one\n\nClaude Code now remembers the previous sign-in and the tokens it handed out, so an outdated one can be swapped for the current token\n\n**What**\n\nA token is the credential Claude Code uses to prove you are signed in. Claude Code now remembers the previous sign-in and which tokens it has handed out. When an outdated token from the same sign-in comes back, it can be swapped for the current one. Previously, resetting this state only cleared the token.\n\n**Why**\n\nSomething still holding an older token from the same sign-in can keep working instead of failing.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}