{"version":"2.1.317","anchor":"ripgrep-timeout-message-now-built-by-a-helper","canonical_anchor":"ripgrep-timeout-message-now-built-by-a-helper","heading":"Search timeout message no longer has a fixed number of seconds","tier":"notice","area":"Search","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/ripgrep-timeout-message-now-built-by-a-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Search timeout message no longer has a fixed number of seconds\n\nThe search timeout message no longer states a fixed 20 or 60 seconds; Claude Code now works out that part of the wording\n\n**Unclear.** It is unclear whether the search time limit itself changed or can be set, or only how the message is worded.\n\n**What**\n\nWhen a file search times out, the message used to state a fixed time: 60 seconds on WSL (Windows Subsystem for Linux) and 20 seconds elsewhere. That part of the message is now generated. It still ends with \"The search may have matched files but did not complete in time.\"\n\n**Why**\n\nThe time limit shown in the message is no longer fixed.\n\n- Area: Search\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}