{"version":"2.1.321","anchor":"pooled-connection-idle-limit-also-controlled-by-a-tenant-set","canonical_anchor":"pooled-connection-idle-limit-also-controlled-by-a-tenant-set","heading":"Some organizations' settings can now apply the idle limit to reused connections","tier":"internal","area":"Network","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/pooled-connection-idle-limit-also-controlled-by-a-tenant-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Some organizations' settings can now apply the idle limit to reused connections\n\nThe limit on how long an unused pooled connection stays open can now also be switched on by an organization-level setting\n\n**What**\n\nClaude Code keeps a pool of open connections to reuse, and can close one that has sat unused too long. That idle limit can now also be applied by a setting tied to your organization's account, `pooledConnectionsHaveTenantIdleLimit`. Before, it depended only on Claude Code's own checks.\n\n`CLAUDE_CODE_DISABLE_POOLED_CONNECTION_IDLE_LIMIT` still turns the idle limit off completely.\n\n**Why**\n\nThis changes when reused connections are closed for some organizations, which can affect errors caused by stale connections. If you need the old behaviour, the environment variable above still overrides it.\n\n- Area: Network\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}