{"version":"2.1.281","anchor":"oauth-credential-change-check-tracks-the-token-claude-code-s","canonical_anchor":"oauth-credential-change-check-tracks-the-token-claude-code-s","heading":"OAuth credential change-check tracks the token Claude Code saved itself","tier":"internal","area":"Auth","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/oauth-credential-change-check-tracks-the-token-claude-code-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### OAuth credential change-check tracks the token Claude Code saved itself\n\nResetting the OAuth credential change-check now also forgets the access token Claude Code last saved itself\n\n**Unclear.** The finding does not say what Claude Code does differently once it knows a token was its own.\n\n**What**\n\nClaude Code watches its saved login credentials for changes. It now remembers the last access token it saved itself, and `resetChangeCheck` clears that too. An access token is the credential used for requests after you log in with OAuth.\n\n**Why**\n\nThe change-check can tell tokens Claude Code wrote apart from tokens changed some other way.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}