{"version":"2.1.304","anchor":"oauth-stored-login-plan-is-recorded-from-the-profile-and-ver","canonical_anchor":"oauth-stored-login-plan-is-recorded-from-the-profile-and-ver","heading":"Stored sign-ins now record where the plan came from and when it was checked","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/oauth-stored-login-plan-is-recorded-from-the-profile-and-ver","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Stored sign-ins now record where the plan came from and when it was checked\n\nSaved sign-ins now record whether the plan came from sign-in or the profile, and when it was verified, and refuse downgrades\n\n**What**\n\nWhen you sign in, Claude Code saves your login, including your plan (`subscriptionType`). It now also keeps:\n\n- `subscriptionTypeSource`: either `'sign_in'` or `'profile'`, saying where the plan came from.\n\n- `subscriptionTypeVerifiedAt`: when the plan was last verified.\n\nThe credentials object copies both next to `subscriptionType`. After your profile is fetched, the stored plan is written back, with the log line \"OAuth: recorded the stored login plan\". A downgrade is refused, and the profile is fetched again when the verification is out of date. Before, only `subscriptionType` and `rateLimitTier` were saved.\n\n**Why**\n\nThe plan shown for a saved login is checked against your profile instead of trusting whatever was stored at sign-in.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}