[BUG] VSCode extension: ripgrep path hardcoded to CI build path (ENOENT on Windows)

Resolved 💬 3 comments Opened Mar 15, 2026 by Kianv111 Closed Mar 19, 2026

Preflight Checklist

  • [ ] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Ripgrep search failed A system error occurred
(spawn C:\home\runner\work\claude-cli-internal\claude-cli-internal\vendor\ripgrep\x64-win32\rg.exe ENOENT)

What Should Happen?

Expected: Extension uses its bundled rg.exe relative to install path
Actual: Path is hardcoded to CI build machine path which doesn't exist on end-user machines

Error Messages/Logs

2026-03-15 11:01:05.444 [info] Received message from webview: {"type":"request","requestId":"gp61fbxiz55","request":{"type":"list_files_request","pattern":""}}
2026-03-15 11:01:05.449 [error] Ripgrep search failed A system error occurred (spawn C:\home\runner\work\claude-cli-internal\claude-cli-internal\vendor\ripgrep\x64-win32\rg.exe ENOENT)
2026-03-15 11:01:05.451 [warning] Ripgrep search failed, falling back to VSCode findFiles: Error: spawn C:\home\runner\work\claude-cli-internal\claude-cli-internal\vendor\ripgrep\x64-win32\rg.exe ENOENT

Steps to Reproduce

  1. Install Claude Code VSCode extension on Windows
  2. Open any workspace
  3. Use @ mention
  4. Check output log → Claude Code

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.76

Platform

Other

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

Workaround tried: winget install BurntSushi.ripgrep.MSVC — does not help because path is hardcoded, not resolved from PATH

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗