{"version":"2.1.315","anchor":"https-agent-pooled-sockets-tied-to-check-switches-idle-limi","canonical_anchor":"https-agent-pooled-sockets-tied-to-check-switches-idle-limi","heading":"Reused secure connections are closed when certain settings change","tier":"notice","area":"Network Security","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/https-agent-pooled-sockets-tied-to-check-switches-idle-limi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Reused secure connections are closed when certain settings change\n\nWith client or custom CA certificates, Claude Code now closes a reused connection when certain connection settings have changed since it opened\n\n**What**\n\nWhen Claude Code connects using mTLS (where your computer also presents a certificate to prove who it is) or custom CA certificates, it keeps a pool of open connections to reuse. Two things about that pool changed:\n\n- Each connection is now tagged with a fingerprint of certain connection settings. If those settings have changed by the time the connection is reused, Claude Code closes it.\n\n- Connections with different fingerprints are kept in separate pools.\n\n`CLAUDE_CODE_DISABLE_POOLED_CONNECTION_IDLE_LIMIT` still turns off the limit on how long an unused connection stays open.\n\n**Why**\n\nThis makes it less likely that Claude Code reuses an old connection after your sign-in or certificate setup has changed.\n\n- Area: Network Security\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}