Login now trusts a fixed set of Anthropic API origins unless you point it at a custom OAuth URL.
What's wrong with this entry?
OAuth origin validation now trusts a fixed set of Anthropic API origins rather than only the origin derived from the configured base API URL.
- If CLAUDE_CODE_CUSTOM_OAUTH_URL is set, only the configured origin is trusted and the fixed set is not consulted.
- Rejections still report a reason:
not_https,userinfo_or_portoruntrusted_origin.
https://api-staging.anthropic.com
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.227
Auth failures now name the credential source
Both mention custom auth
-
v2.1.227
Auth token and custom header failures now say which value is wrong
Both mention custom auth
-
v2.1.229
OAuth token warning no longer tells you to unset the variable
Both mention oauth auth