Unclear It is not clear which requests use this new connection handling, or what setting CLAUDE_CODE_DISABLE_HTTPS_AGENT_KEEPING does to it.
What
To save time, Claude Code keeps secure (HTTPS) connections open and reuses them for later requests. New connection handling changes when those kept connections are thrown away.
- Changed security settings: Claude Code notes which values of
NODE_TLS_REJECT_UNAUTHORIZED,BUN_TLS_REFUSE_DISTRUSTED_KEYSandCLAUDE_CODE_DISABLE_HTTPS_AGENT_KEEPINGwere in force when each connection was opened. If those values have since changed and no request is waiting on that connection, Claude Code closes it. - Server errors: after a server answers with a 5xx error (a server-side failure), the connection is closed. Idle connections to the same host and port are closed too, so the next request opens a fresh connection. 501 and 529 are the exceptions.
This build also adds a way to reach an OpenTelemetry collector through a proxy tunnel. OpenTelemetry is a standard for sending usage and performance data. It also adds an error for when opening a connection takes too long.
Why
Connections are now reused differently after server errors, which can affect how reliably requests to the API go through.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
It is not clear which requests use this new connection handling, or what setting `CLAUDE_CODE_DISABLE_HTTPS_AGENT_KEEPING` does to it.