You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.288,
ImprovementsSection of the release
What
When 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:
You are logged in for now, but the new credentials were not saved
Your previous login is still in place
You are not logged in
The 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.
Why
Before, 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear when the Escape hint to continue without logging in is shown.
Anthropic's release notes agreeFixed /login reporting "Login successful" when credentials could not be saved to secure storage; it now shows the failure, and offers a…
