Login reports when credentials could not be saved and can be skipped

What

After you sign in, Claude Code stores your credentials so you stay logged in. It now checks that this worked.

• If the credentials were not saved, the login screen enters a new storage_failed state and shows Claude Code login needs attention: credentials could not be saved, or credentials may not have been saved when the failure might be temporary. Before, it always reported success.
• Messages name where credentials are stored, for example the macOS Keychain or the credentials file or Windows Credential Manager. A new reason, auth_storage_failure, is added.
• A new allowContinueWithoutLogin option adds a way to leave the screen without logging in. The first-run setup flow turns it on, so that login step can be skipped.
• After an error, the claude.ai and Console login paths now restart from the step where you choose how to log in instead of from the very beginning.
• The Resume this conversation? dialog now passes an input guide to its wrapper.

Why

If your keychain or credentials file could not be written, you used to see a success message and then find yourself logged out later. You now learn at once that something went wrong and where, and setup no longer has to stop at the login step.