{"version":"2.1.318","anchor":"login-restore-result-now-reflects-a-second-step","canonical_anchor":"login-restore-result-now-reflects-a-second-step","heading":"Login restore after switching accounts now depends on an extra check","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/login-restore-result-now-reflects-a-second-step","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Login restore after switching accounts now depends on an extra check\n\nAfter you switch accounts or sign out, Claude Code now waits on one more step before reporting that your previous login was restored\n\n**Unclear.** What the extra step checks is not known, so it is unclear which situations now stop counting as a restored login.\n\n**What**\n\nWhen you switch to another account or sign out, Claude Code tries to bring back the login you had before. It then reports whether that worked. That report of success now also depends on a further step that Claude Code waits for after its earlier step. Before, it depended only on the earlier step and on whether the replaced login could be brought back at all.\n\n**Why**\n\nThis can change when Claude Code tells you that your previous login was restored. A case that used to count as restored may now be reported as not restored.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}