{"version":"2.1.251","anchor":"subscription-and-api-key-caches-can-now-be-cleared-explicitl","canonical_anchor":"subscription-and-api-key-caches-can-now-be-cleared-explicitl","heading":"Subscription and API-key caches can now be cleared explicitly","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/subscription-and-api-key-caches-can-now-be-cleared-explicitl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Subscription and API-key caches can now be cleared explicitly\n\nLogging in or out now clears cached key and subscription state properly.\n\n**What**\n\nThe caches holding your primary API key and detected subscription now sit behind an object with a clear operation, called on logout, login and keychain changes, so stale auth state is dropped instead of lingering.\n\n**Details**\n\n- New helpers expose the normalized subscription tier (max, pro, team or enterprise) and the rate-limit tier.\n- Both are available only when you are signed in via OAuth; an API key or a `CLAUDE_CODE_OAUTH_TOKEN` override skips them.\n\n**Evidence**\n\n`case \"max\":`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}