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.269,
ImprovementsSection of the release
What
When Claude Code checks your OAuth token (used for signing in) against the server, it used to fail with one generic error. Now the underlying check returns a structured result: either success with the validated data, or failure with a specific reason — one of unauthorized, forbidden, proxy, http_error, timeout, dns, connect, tls, or network_error — worked out from the actual HTTP status code or network error encountered.
Why
This lets Claude Code (and anyone debugging a login problem) tell the difference between, say, a DNS lookup failure, a proxy issue, and an expired token, instead of seeing the same undifferentiated error for every kind of failure.
