Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.227 Home All releases ←olderv2.1.226 v2.1.228newer→
Claude Code v2.1.227

Enterprise OIDC login can route identity provider requests through a proxy

Use it now
Useful3 Signal3
Auth Notable

Enterprise OIDC logins can route identity provider requests through your configured HTTPS proxy.

oidc.use_proxyHTTPS_PROXYHTTP_PROXY
What

OIDC configuration accepts a new optional use_proxy boolean. Set it to true and requests to your identity provider go through HTTPS_PROXY/HTTP_PROXY. Leave it out while a proxy is configured and Claude Code now warns that those requests currently go direct and will follow the proxy by default in a future release, pointing you at oidc.use_proxy: true to adopt the new behaviour now or false to silence the warning.

Details
  • Setting the key to true with no usable proxy variable also warns, and requests still go direct.
  • Only reachable on installs that use OIDC identity provider login.
Evidence

oidc.use_proxy is set but no usable HTTPS_PROXY/HTTP_PROXY is set; IdP requests go direct

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.

See this entry in the whole of v2.1.227 →