{"version":"2.1.300","anchor":"auto-tool-search-stays-on-once-the-conversation-declared-too","canonical_anchor":"auto-tool-search-stays-on-once-the-conversation-declared-too","heading":"Automatic tool search stays on once a conversation has used it","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/auto-tool-search-stays-on-once-the-conversation-declared-too","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Automatic tool search stays on once a conversation has used it\n\nIn automatic tool search mode, once a conversation has set up tool search it stays enabled instead of being rechecked against the usage threshold each time\n\n**What**\n\nTool search lets Claude Code hold back some tools and load them only when the model searches for them, which saves room in the conversation. In automatic mode, Claude Code decides whether to turn tool search on by checking how much of the context window (the amount of conversation the model can hold at once) the tools would use against a threshold.\n\nThat check used to run every time. Now, if the conversation has already set up the `ToolSearch` tool, Claude Code keeps tool search on without running the threshold check again.\n\n**Why**\n\nBefore, if usage dropped below the threshold partway through a conversation, tools that were being loaded on demand could disappear. Keeping tool search on stops that from happening mid-conversation.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}