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

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:

Update VS Code to 1.122.0
Open any extension that resolves VSCode's bundled ripgrep via vscode.env.appRoot
(e.g. Todo-Tree, Roo Code / Zoo Code codebase indexing)
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.

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.

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

same issue here in macos

This happened to me, but inside a devcontainer

I confirm the same issue with todo-tree

Same Questions

Henning Dieterichs (@hediet)

Henning Dieterichs (@hediet) FYI

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.

Unfortunately you have to add the full absolute path to the ripgrep location setting.
It does not work to just add rg, even if ripgrep is in your PATH settings.
That means it isn’t platform-independent nor device-independent.

I've fixed the issue in Ubuntu 24.04 installing the ripgrep package systemwide and configuring the Todo-Tree extension to use it.

First, install the package:

sudo apt update && sudo apt install ripgrep

Run the following command to find the exact package location after installation:

which rg

Then, add the following line in your VSCode settings.json file with the path returned by the previous command, in my case:

"todo-tree.ripgrep.ripgrep": "/usr/bin/rg"

VSCode shouldn't show the error again after restart.

This worked for me, thanks!!!

Ran into this this morning. (Windows 11) Searched my system for rg.exe and found a bunch of them. Added C:\Users\USERNAME\AppData\Local\Programs\cursor\resources\app\node_modules\@vscode\ripgrep\bin\rg.exe to the ripgrep location setting in VSCode and all is well again.

Thanks for this. I'm on Windows 10. Any idea how I can fix this location issue? I found my location at C:\Users\User\AppData\Local\Microsoft\WinGet\Links\rg.exe, but I have no idea how to update the vscode location setting. Thanks.

nigelp

nigelp See my comment above:
#318691 (comment)

Thanks very much. Claude actually gave me a symlink kludge workaround script, which seems to have fixed the problem.

for vscode 1.123.0, Ubuntu 22.04

sudo mkdir -p /usr/share/code/resources/app/node_modules/@vscode/ripgrep/bin

sudo ln -s /usr/share/code/resources/app/node_modules/@vscode/ripgrep-universal/bin/linux-x64/rg /usr/share/code/resources/app/node_modules/@vscode/ripgrep/bin/rg

work for roo code, kilo code

Roo code FIX For mac os M series (VS code Version: 1.122.1)

Make directory mkdir -p "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep/bin"

link ripgrep from darwin-arm64 to new fodler ln -s "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep-universal/bin/darwin-arm64/rg" "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep/bin/rg"

Don't use Roo Code anymore, it's archived. Use the actively maintained fork, Zoo Code, instead: https://github.com/Zoo-Code-Org/Zoo-Code

Roo code FIX For mac os M series (VS code Version: 1.122.1)
Make directory mkdir -p "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep/bin"
link ripgrep from darwin-arm64 to new fodler ln -s "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep-universal/bin/darwin-arm64/rg" "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep/bin/rg"

Don't use Roo Code anymore, it's archived. Use the actively maintained fork, Zoo Code, instead: https://github.com/Zoo-Code-Org/Zoo-Code

Does zoo-code brought back the xml tool call suport? I am stuck on a old build of roocode because of that

Roo code FIX For mac os M series (VS code Version: 1.122.1)
Make directory mkdir -p "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep/bin"
link ripgrep from darwin-arm64 to new fodler ln -s "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep-universal/bin/darwin-arm64/rg" "/Applications/Visual Studio Code.app/Contents/Resources/app/node_modules/@vscode/ripgrep/bin/rg"

Don't use Roo Code anymore, it's archived. Use the actively maintained fork, Zoo Code, instead: https://github.com/Zoo-Code-Org/Zoo-Code

Does zoo-code brought back the xml tool call suport? I am stuck on a old build of roocode because of that

Yes, that's been addressed in the latest releases. Please migrate to Zoo Code, Roo Code is no longer an option.

The trouble with all of this is I have to repeat whatever fix I use every time VS Code updates. So I've now disabled updates, which is not an ideal situation, but I'm sick to death of having to deal with this problem.

I ran into the same issue on macOS (Apple Silicon) with VS Code 1.124.2 and Roo Code 3.54.0.
In my case, Roo would hang indefinitely at "API Request..." for any workspace, and the Developer Console showed:
Error: Could not find ripgrep binary
The existing discussion about VS Code's ripgrep layout changes pointed me in the right direction, so I dug a little further into Roo's extension code to understand what it was looking for.
It appears Roo is checking for a ripgrep binary directly under:
node_modules/@vscode/ripgrep/bin/rg
However, my VS Code installation contains:
node_modules/@vscode/ripgrep/bin/darwin-arm64/rg
The binary exists and is executable, but there is no bin/rg at the location Roo expects.
As a test, I created a symlink:
node_modules/@vscode/ripgrep/bin/rg
→
node_modules/@vscode/ripgrep/bin/darwin-arm64/rg
After reloading the VS Code window, Roo immediately started working normally and was able to analyze project files again.
I'm not certain whether this affects all Apple Silicon installations or only some VS Code versions, but hopefully the path difference helps narrow down the root cause.

I ran into the same issue on macOS (Apple Silicon) with VS Code 1.124.2 and Roo Code 3.54.0. In my case, Roo would hang indefinitely at "API Request..." for any workspace, and the Developer Console showed: Error: Could not find ripgrep binary The existing discussion about VS Code's ripgrep layout changes pointed me in the right direction, so I dug a little further into Roo's extension code to understand what it was looking for. It appears Roo is checking for a ripgrep binary directly under: node_modules/@vscode/ripgrep/bin/rg However, my VS Code installation contains: node_modules/@vscode/ripgrep/bin/darwin-arm64/rg The binary exists and is executable, but there is no bin/rg at the location Roo expects. As a test, I created a symlink: node_modules/@vscode/ripgrep/bin/rg → node_modules/@vscode/ripgrep/bin/darwin-arm64/rg After reloading the VS Code window, Roo immediately started working normally and was able to analyze project files again. I'm not certain whether this affects all Apple Silicon installations or only some VS Code versions, but hopefully the path difference helps narrow down the root cause.

As I said above: "Don't use Roo Code anymore, it's archived. Use the actively maintained fork, Zoo Code, instead: https://github.com/Zoo-Code-Org/Zoo-Code"

Thanks very much. Very clear guide. :)

For Todo-tree, I found that you don't have to copy the executable, instead just go to vscode settings, find Todo-tree › Ripgrep: Ripgrep setting and simply point it to the new location.

Navigation Menu

Repository navigation

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

8 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

Description

Activity

Hibrix-net commented on May 28, 2026

bitray commented on May 28, 2026

lmartininwg commented on May 28, 2026

tdanh2k commented on May 28, 2026

gitenstuff commented on May 28, 2026

Praying commented on May 28, 2026

dmitrivMS commented on May 28, 2026

hediet commented on May 28, 2026

8 remaining items

Franky1 commented on Jun 2, 2026

Rafdal commented on Jun 4, 2026

nigelp commented on Jun 4, 2026

Franky1 commented on Jun 4, 2026

nigelp commented on Jun 4, 2026

ch097711 commented on Jun 5, 2026

Hibrix-net commented on Jun 5, 2026

3750gustavo commented on Jun 5, 2026

Hibrix-net commented on Jun 5, 2026

nigelp commented on Jun 12, 2026

thatmacguy commented on Jun 14, 2026

Hibrix-net commented on Jun 15, 2026

nigelp commented on Jun 23, 2026

Swor71 commented on Jul 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions