{"version":"2.1.321","anchor":"fetch-sessions-get-a-per-client-keep-alive-idle-timeout-key","canonical_anchor":"fetch-sessions-get-a-per-client-keep-alive-idle-timeout-key","heading":"Network connections are kept separate per client and can close after idle time","tier":"internal","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/fetch-sessions-get-a-per-client-keep-alive-idle-timeout-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Network connections are kept separate per client and can close after idle time\n\nClaude Code now keeps reused network connections separate for each client and can close idle ones after a set time\n\n**What**\n\nClaude Code reuses open network connections instead of opening a new one for every request. It now keeps a separate set of reusable connections for each client, so connections for different customers do not mix.\n\nFor one of its HTTP clients, Claude Code reads an idle limit and closes a connection that has been unused for that long. It reuses a stored connection only when both the idle limit and the security (TLS) settings match. Before, it reused a connection whenever the security settings matched.\n\n**Why**\n\nThis changes when connections are reused and when idle ones are closed.\n\n- Area: Network\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}