{"version":"2.1.318","anchor":"login-now-warns-when-the-previous-login-may-remain","canonical_anchor":"login-now-warns-when-the-previous-login-may-remain","heading":"Signing in can keep the stored login and warns when the previous one may remain","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/login-now-warns-when-the-previous-login-may-remain","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Signing in can keep the stored login and warns when the previous one may remain\n\nRe-login to the same organisation can keep the stored login, and sign-in now tells you when a previous account or API key may still be stored\n\n**What**\n\nSigning in and switching accounts changed in two ways:\n\n- `keepStoredLogin`: a new option for the reset that runs when you change account. When it is set, one cleanup step is skipped, so signing in again to the same organisation can keep the login that is already stored.\n\n- `departingLoginMayRemain`: sign-in now notes when the previous login may still be stored. In that case a new message says \"Sign in again to take your previous account or API key off the config file.\" The `claude_authenticate` flow used by apps built on the SDK writes this notice to stderr, the error output stream. The result reported when storing the login fails also includes this information.\n\n**Why**\n\nSwitching accounts could leave old credentials in the config file without telling you. Now you are told, and you can sign in again to remove them.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}