What
When you sign in, Claude Code normally starts a small local listener that receives the result from your browser. If that listener could not start, login failed.
- Now login continues with a manual URL and asks you to paste the code shown after signing in, at the prompt "Paste code here > ".
- The login screen says "Use the URL below to sign in" instead of "Browser didn't open? Use the url below to sign in".
claude auth loginin a terminal prints "Sign in at:" with the URL and waits for the code; Ctrl-D closes the prompt and stops the login.- Running out of file handles (EMFILE or ENFILE) still stops login with an error.
- If the fallback cannot be used, you see "Couldn't start the local listener that receives the browser sign-in. Try again." with " Run with --debug for the underlying error." added.
- Separately, the sign-in URL builder can add one extra permission scope through a new
alsoRequestScopeoption; no caller was found using it.
Why
Login can work on headless or remote machines and where the local port is blocked, and failures point you to --debug.
Names in the bundleclaude auth login
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude auth login, on Authentication.
* **Earlier sign-in**: you ran [`claude auth login`](/docs/en/cli-reference#cli-commands) in your shell before your first session, or you rebuilt a dev container that keeps your credentials in a [volume](/docs/en/devcontainer#persist-authe…authentication see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude auth login, on Authentication.