{"version":"2.1.317","anchor":"grepsearch-timeouts-can-now-reject-as-incomplete-results","canonical_anchor":"grepsearch-timeouts-can-now-reject-as-incomplete-results","heading":"Searches cut short can now fail with a note that results are incomplete","tier":"notice","area":"Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/grepsearch-timeouts-can-now-reject-as-incomplete-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Searches cut short can now fail with a note that results are incomplete\n\nIn a stricter mode, a search that is cut short now fails with a message that more matches may exist, instead of returning partial results\n\n**Unclear.** Which of Claude's searches run in this stricter mode is not stated.\n\n**What**\n\nWhen Claude searches through files and the search is cut short, for example by taking too long, the partial results used to come back with no warning. In a stricter mode that some searches use, the search now fails instead. The message says the results are incomplete and that \"more matches may exist\", and suggests searching a more specific path or pattern.\n\n**Why**\n\nClaude is told when a search did not finish, so it does not treat a partial list of matches as the full picture and can try a narrower search.\n\n- Area: Search\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}