Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.301 ·

File searches that fail early now stop with an error straight away

When the search program behind file searches fails without results, some searches now stop with an error at once instead of going through general handling

You'll notice Improvements
JSON All of v2.1.301
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.301,
ImprovementsSection of the release

Unclear Which searches ask to treat bad input as an error is not stated, so whether the Grep or Glob tools show a different error is unknown.

What

Claude Code uses a program called ripgrep to search files. When ripgrep exits unexpectedly without finding anything, a search that has asked to treat bad input as an error now stops with an error immediately. Before, the failure was logged and then handled the general way. The errors for a search that times out or is cancelled are now built in one shared place.

Why

This may change the error message you see when a file search goes wrong.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich searches ask to treat bad input as an error is not stated, so whether the Grep or Glob tools show a different error is unknown.

See this entry in the whole of v2.1.301 →

Feedback