{"version":"2.1.288","anchor":"login-shows-a-dedicated-screen-when-credentials-cannot-be-sa","canonical_anchor":"login-shows-a-dedicated-screen-when-credentials-cannot-be-sa","heading":"Login now tells you when your sign-in worked but could not be saved","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/login-shows-a-dedicated-screen-when-credentials-cannot-be-sa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Login now tells you when your sign-in worked but could not be saved\n\nIf sign-in succeeds in the browser but your credentials cannot be stored, login now shows a dedicated screen explaining what happened and what to do\n\n**Unclear.** It is not clear when the Escape hint to continue without logging in is shown.\n\n**What**\n\nWhen you log in, Claude Code opens your browser to sign in and then saves the resulting credentials in a credential store, such as your system keychain or a credentials file. If the browser sign-in works but that save fails, the login flow now shows a dedicated screen. It says which of three situations you are in:\n\n- You are logged in for now, but the new credentials were not saved\n\n- Your previous login is still in place\n\n- You are not logged in\n\nThe screen suggests two ways forward: fix access to the credential store and run `\/login` again, or run `claude setup-token` and set the `CLAUDE_CODE_OAUTH_TOKEN` environment variable (a setting your shell passes to programs). Both this screen and the general login error screen can also show a hint that pressing Escape lets you continue without logging in.\n\n**Why**\n\nBefore, a failure to save credentials could leave you logged out with no explanation. Now you see that the save is what failed, and how to work around it.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}