{"version":"2.1.317","anchor":"direct-search-slots-http-agent-socket-cleanup-and-group-po","canonical_anchor":"direct-search-slots-http-agent-socket-cleanup-and-group-po","heading":"Small changes to search limits, network connections and usage readings","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/direct-search-slots-http-agent-socket-cleanup-and-group-po","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Small changes to search limits, network connections and usage readings\n\nClaude Code adds a way to claim a direct search slot, changes how idle network connections are cleaned up, and drops overage from group pool usage\n\n**Unclear.** It is not clear what any of the three changes does in practice, including whether you will see group pool overage anywhere.\n\n**What**\n\nThree small changes:\n\n- Search: Claude Code gained a way to claim a slot for a direct search.\n\n- Network connections: cleaning up connections no longer sets the number of idle connections kept open to zero.\n\n- Usage readings: when usage comes from a group pool, the overage figure, meaning usage past the included amount, is removed from the readings.\n\n**Why**\n\nThese touch rate limiting, which is how Claude Code caps how much it does at once, and how it handles network connections.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}