[Regression 1.122.0] Bundled ripgrep binary path changed, breaking extensions that resolve rg via vscode.env.appRoot (Todo-Tree, Roo Code/Zoo Code)

[Hibrix-net]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.122.0 (6a49527, x64, user setup)
• OS Version: Windows 11 x64

Steps to Reproduce:

1. Update VS Code to 1.122.0
2. Open any extension that resolves VSCode's bundled ripgrep via vscode.env.appRoot
   (e.g. Todo-Tree, Roo Code / Zoo Code codebase indexing)
3. Extension fails with: Failed to find vscode-ripgrep / Could not find ripgrep binary

Root cause: VSCode 1.122.0 changed the internal directory structure — the bundled rg.exe
is now located at:
resources/app/<commitHash>/resources/app/node_modules/@vscode/ripgrep-universal/bin/win32-x64/rg.exe

Previous versions placed it at:
resources/app/node_modules/@vscode/ripgrep/bin/win32-x64/rg.exe

Extensions resolving ripgrep via vscode.env.appRoot + standard relative paths no longer
find the binary. System-installed ripgrep (rg in PATH) is also not used as fallback.

Confirmed affected extensions: Todo-Tree, Zoo Code (Roo Code fork) codebase indexing
Workaround: None fully working. Installing ripgrep system-wide via Chocolatey
(choco install ripgrep) does not fix extensions that rely on the bundled binary path.

[Hibrix-net]

Update: found a workaround.

The new path in 1.122.0 is:
resources/app/<commitHash>/resources/app/node_modules/@vscode/ripgrep-universal/bin/win32-x64/rg.exe

Workaround — copy the binary to the legacy path extensions expect:

mkdir "%LOCALAPPDATA%\Programs\Microsoft VS Code<commitHash>\resources\app\node_modules@vscode\ripgrep\bin"
copy "%LOCALAPPDATA%\Programs\Microsoft VS Code<commitHash>\resources\app\node_modules@vscode\ripgrep-universal\bin\win32-x64\rg.exe" "%LOCALAPPDATA%\Programs\Microsoft VS Code<commitHash>\resources\app\node_modules@vscode\ripgrep\bin\rg.exe"

Restart VS Code after.

[bitray]

Same issue as me... And Zoo Code can not access the server

[lmartininwg]

same issue here in macos

[tdanh2k]

This happened to me, but inside a devcontainer

[gitenstuff]

I confirm the same issue with todo-tree

[Praying]

Same Questions

[dmitrivMS]

Henning Dieterichs (@hediet) FYI

[hediet]

This needs to be fixed in the extensions.
An extension must not depend on the internal node_modules folder (or any internals/undocumented API) of VS Code, or it might break just like this one day.

Until vscode offers ripgrep api support, extensions should ship their own ripgrep exec (e.g. by bundling @vscode/ripgrep-universal).

This is unfortunate for Todo-Tree which does not seem to be maintained anymore, but also a good opportunity to use GitHub Copilot to create a new extension.