{"version":"2.1.315","anchor":"ripgrep-timeout-kill-now-has-a-watchdog","canonical_anchor":"ripgrep-timeout-kill-now-has-a-watchdog","heading":"File searches no longer hang when ripgrep fails to exit after a timeout","tier":"notice","area":"File Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/ripgrep-timeout-kill-now-has-a-watchdog","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### File searches no longer hang when ripgrep fails to exit after a timeout\n\nIf ripgrep does not exit after being killed for timing out, the search now ends with an error instead of waiting forever\n\n**What**\n\nClaude Code's file search tools, Grep and Glob, use a program called ripgrep. When a search runs too long, Claude Code kills ripgrep. Until now, if ripgrep never confirmed that it had closed, the search could wait indefinitely.\n\nClaude Code now ends the search anyway. It logs that ripgrep did not report closing after the kill, and the search fails with the message \"ripgrep did not exit after the timeout kill\".\n\n**Why**\n\nA stuck ripgrep process can no longer freeze Grep or Glob. You get an error you can act on instead of a search that never finishes.\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"}