{"version":"2.1.292","anchor":"ripgrep-unreadable-target-error-is-now-explicit","canonical_anchor":"ripgrep-unreadable-target-error-is-now-explicit","heading":"Searches that cannot read their target now say they failed","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/ripgrep-unreadable-target-error-is-now-explicit","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Searches that cannot read their target now say they failed\n\nWhen a search cannot read the place it was asked to search, Claude is told the search failed rather than that it found nothing\n\n**What**\n\nClaude Code searches files with a tool called ripgrep. When ripgrep cannot read the file or folder it was asked to search, Claude now gets a specific error. The error says the search failed and that \"This is not a \"no matches\" result.\" It also tells Claude not to fall back to searching the folders itself with a shell command.\n\n**Why**\n\nWithout this, a failed search could look the same as a search that found nothing, and Claude could wrongly conclude that something does not exist in your files. It also stops Claude from starting a slow search of the whole folder as a workaround.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}