You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
NetworkArea: what it touches
ImprovementsKind: in v2.1.317,
ImprovementsSection of the release
Unclear It is not clear whether this repair is switched on for everyone or depends on a setting.
What
A secure connection relies on a chain of certificates, digital credentials that prove a server is who it says it is. When checking that chain fails with one of these errors, Claude Code can now read the certificates the server presents:
UNABLE_TO_GET_ISSUER_CERT_LOCALLY
UNABLE_TO_VERIFY_LEAF_SIGNATURE
UNABLE_TO_GET_ISSUER_CERT
It checks whether the chain needs a certificate from your system that Claude Code's list of trusted authorities left out, and adds that certificate back if so. If you use an HTTP CONNECT proxy, it reads the certificates through it. It does not do this through an https:// proxy. The check is skipped when ANTHROPIC_UNIX_SOCKET is set.
Why
This may fix certificate errors on corporate networks where connections used to fail.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether this repair is switched on for everyone or depends on a setting.
Anthropic's release notes agreeFixed OpenTelemetry exports to an https:// endpoint through a proxy never being sent when they started while another export was still in…
