Search Tool Returns Zero Results on Windows Platform

Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Activity 10 comments · opened Aug 3, 2025 · closed Aug 6, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
The search tool returns 0 files and 0 lines. (win32)

Environment Info

  • Platform: win32
  • Terminal: rider
  • Version: 1.0.67
  • Feedback ID: 2ec9b814-e568-408a-9a3c-0fab93bc9222

Errors

[{"error":"Error: Plugin source missing\n    at vSG (B:/~BUN/root/claude.exe:1283:30201)\n    at vSG (B:/~BUN/root/claude.exe:1283:30900)\n    at Dv9 (B:/~BUN/root/claude.exe:1284:4916)\n    at Dv9 (B:/~BUN/root/claude.exe:1284:4980)\n    at Wv9 (B:/~BUN/root/claude.exe:1284:2196)\n    at Wv9 (B:/~BUN/root/claude.exe:1284:2499)\n    at <anonymous> (B:/~BUN/root/claude.exe:1285:3605)\n    at <anonymous> (B:/~BUN/root/claude.exe:1285:3800)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-08-03T23:35:14.103Z"},{"error":"Error: String not found in file. Failed to apply edit.\n    at j_ (B:/~BUN/root/claude.exe:1763:737)\n    at renderToolUseRejectedMessage (B:/~BUN/root/claude.exe:2413:1664)\n    at DE (B:/~BUN/root/claude.exe:31:19860)\n    at af (B:/~BUN/root/claude.exe:33:42836)\n    at nf (B:/~BUN/root/claude.exe:33:38359)\n    at FR (B:/~BUN/root/claude.exe:33:38287)\n    at LE (B:/~BUN/root/claude.exe:33:38141)\n    at LK (B:/~BUN/root/claude.exe:33:35204)\n    at j8 (B:/~BUN/root/claude.exe:31:4842)\n    at qX (B:/~BUN/root/claude.exe:33:32450)","timestamp":"2025-08-03T23:39:22.179Z"}]

View original on GitHub ↗

10 Comments

github-actions[bot] · 1 year ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/5014
  2. https://github.com/anthropics/claude-code/issues/164
  3. https://github.com/anthropics/claude-code/issues/1545

If your issue is a duplicate, please close it and 👍 the existing issue instead.

🤖 Generated with Claude Code

ant-kurt collaborator · 1 year ago

Are you on native installer? There are some issues with search we're working to resolve

pavel-zhur · 1 year ago

@ant-kurt yes, native installer.

Pannoniae · 1 year ago

yeah, native installer

ant-kurt collaborator · 1 year ago

Should be resolved in 1.0.70 for Windows native build

Pannoniae · 1 year ago

Thx!<3

GitMurf · 1 year ago
Should be resolved in 1.0.70 for Windows native build

@ant-kurt This is not resolved for me. Still issue. I am using native install on windows running wsl2 to run Claude code. On 1.0.72 and still an issue.

ant-kurt collaborator · 1 year ago

@GitMurf running Claude Code on WSL runs our Linux build. Can you open a new issue with the following details?

  • What distro?
  • x64 or arm?
  • If you run with claude --debug, do you see any logs containing "rg spawn" or "rg error"?
GitMurf · 1 year ago

@ant-kurt I figured out a solution! It is like others have mentioned, an issue with ripgrep custom config, but the problem I had was NOT fixed by the typical USE_BUILTIN_RIPGREP env settings that others have mentioned. Instead I had to set the RIPGREP_CONFIG_PATH to a "dummy" value so it didn't try to load any custom rg config.

I documented the full details / solution here: https://github.com/anthropics/claude-code/issues/4741#issuecomment-3177976916

As for your questions, it was not based on any particular rg config option as I tried just a simple single --ignore as the only thing in my .ripgreprc and it still created the issues in Claude Code. I tried several simple just single settings like --smart-case etc. and they all failed. The only thing that worked for me was setting the config path to a dummy value so CC didn't try to load a custom config at all.

  • Windows 11
  • Windows Terminal
  • WSL2 Arch linux

I would be happy to troubleshoot further to try and get to the bottom of the root cause if you want to ask some follow-up questions? Thanks!

github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.