{"version":"2.1.299","anchor":"tether-threading-disabled-when-documentssearch-results-are","canonical_anchor":"tether-threading-disabled-when-documentssearch-results-are","heading":"Sessions with search results start a fresh request instead of continuing a thread","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/tether-threading-disabled-when-documentssearch-results-are","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Sessions with search results start a fresh request instead of continuing a thread\n\nWhen a conversation contains search result output from a tool, Claude Code now sends a fresh request instead of continuing a message thread\n\n**Unclear.** Whether this threaded way of sending requests is in use at all is not known.\n\n**What**\n\nClaude Code has a way of continuing an earlier request as a thread instead of sending the whole conversation again. That continuation is now skipped whenever the conversation contains search results returned by a tool, and a fresh request is sent instead. Claude Code also now records whether the first request in the chain was sent as a thread.\n\n**Why**\n\nSessions that use a lot of search may reuse less earlier work than they did before.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}