{"version":"2.1.301","anchor":"ripgrep-abnormal-exit-error-with-strict-advice","canonical_anchor":"ripgrep-abnormal-exit-error-with-strict-advice","heading":"A crashed search is no longer mistaken for one with no results","tier":"notice","area":"File Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/ripgrep-abnormal-exit-error-with-strict-advice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### A crashed search is no longer mistaken for one with no results\n\nWhen ripgrep fails, Claude is told the search failed rather than found nothing, and to retry once instead of a slow shell search\n\n**What**\n\nClaude Code searches files with ripgrep, a fast search program. If ripgrep stops abnormally without returning results, Claude now gets a clear error saying \"The search failed, so this is not a 'no matches' result\". The error tells Claude to retry once and not to fall back to a recursive search through the shell. A separate error for searches that time out was also added.\n\n**Why**\n\nBefore, a crashed search could look like a search that found nothing, which could mislead Claude. Now Claude knows to retry instead.\n\n- Area: File Search\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}