{"version":"2.1.288","anchor":"fetch-session-is-now-cached-per-key-instead-of-a-single-glob","canonical_anchor":"fetch-session-is-now-cached-per-key-instead-of-a-single-glob","heading":"Network connections are kept separately per caller","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/fetch-session-is-now-cached-per-key-instead-of-a-single-glob","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Network connections are kept separately per caller\n\nClaude Code now keeps a separate set of network connections per key instead of one shared set that any caller could replace\n\n**Unclear.** What the key is and which parts of Claude Code pass one is not known.\n\n**What**\n\nClaude Code reuses open network connections to save time. It used to keep one shared set of connections for everything and replace it whenever the security settings for those connections changed. It now keeps a separate set for each key, and only replaces a set when its own security settings change.\n\n**Why**\n\nConnections to different places should no longer throw away each other's reusable connections.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}