Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.317 ·

Grep and Glob searches report when they hit their time limit

Grep returns partial matches instead of failing on a timeout, and Grep and Glob results now carry a timedOut flag

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

What

Grep and Glob are the tools Claude uses to search inside files and to find files by name. These searches have a time limit, and their results now say when that limit cut them short:

  • When ripgrep, the search program behind Grep, times out, Grep now returns the partial matches it had collected and sets timedOut, instead of failing. In that case countIsComplete is false.
  • Grep results, including the files_with_matches mode alongside appliedLimit and appliedOffset, gain an optional timedOut field.
  • The Glob output also gains an optional timedOut field. It is true when the time limit stopped the search after the listed paths were read, so more matches may exist, and absent otherwise.
  • When Glob's timedOut is set, the result text starts with a notice, including on a 'No files found' result.
  • ripgrep can now be started with a directory handle (spawnDirFd), and when it cannot be started it raises errors beginning 'The search did not run: …'.

Before, a Grep timeout was an error, and neither tool's result said whether it had been cut short.

Why

A search that ran out of time is no longer mistaken for one that found nothing. In a large project, a slow search now gives usable partial results, and Claude can tell they may be incomplete.

Read from
Names in the bundletimedOut
What the documentation says

See this entry in the whole of v2.1.317 →

Feedback