{"version":"2.1.305","anchor":"oauth-callback-server-start-failure-now-rejects-the-promise","canonical_anchor":"oauth-callback-server-start-failure-now-rejects-the-promise","heading":"Login now fails properly when its local callback server cannot start","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/oauth-callback-server-start-failure-now-rejects-the-promise","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Login now fails properly when its local callback server cannot start\n\nIf the local server that receives OAuth login results cannot start, Claude Code now reports a real error instead of carrying on\n\n**What**\n\nWhen you log in with OAuth (signing in through your browser), Claude Code starts a small server on your computer to receive the result. If that server fails to start, for example because the port it needs is already taken or blocked, Claude Code now raises a proper error, \"Failed to start OAuth callback server\", which keeps the original cause attached.\n\nBefore, the failure was handed back as if it were a normal result, and the message read from the wrong place.\n\n**Why**\n\nAn occupied or blocked port could leave login hanging or misbehaving. Now it fails with a clear error.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}