Bug: Missing ripgrep Binary in Positron 2026.08.1 Breaks Roo Code Extension When a Workspace Folder Is Open
Summary
After updating to Positron 2026.08.1, the Roo Code extension (v3.54.0) fails to connect to the AI API when any workspace folder is opened. The extension works correctly when no folder is opened (empty window). The root cause is that the ripgrep binary (rg.exe) is not bundled with this Positron release, and the Roo Code extension depends on it for file-system operations. This issue did not occur in prior Positron versions.
Environment
| Item |
Value |
| Positron version |
2026.08.1 |
| VS Code base version |
1.124.0 |
| Node.js version |
v24.15.0 |
| OS |
Windows 11 |
| Installation path |
D:\Program Files\Positron\ |
| Roo Code extension |
rooveterinaryinc.roo-cline v3.54.0 (installed via Open VSX) |
| Ripgrep bundled |
❌ No — @vscode/ripgrep not found under Positron installation or extension directories |
Steps to Reproduce
- Update Positron to version 2026.08.1.
- Install the Roo Code extension (v3.54.0) from Open VSX.
- Open any workspace folder (e.g.,
D:\test).
- Open the Roo Code sidebar panel.
- Attempt to send a message to the AI.
Expected Behavior
The Roo Code extension should connect to the configured AI API and respond normally, regardless of whether a workspace folder is open.
Actual Behavior
-
The Roo Code panel shows "Connecting to API..." indefinitely and never establishes a connection.
-
The extension's internal file-listing operation throws the following error:
Error: Could not find ripgrep binary
at ... rooveterinaryinc.roo-cline-3.54.0-universal\dist\extension.js:853:12306
at async xO (...extension.js:853:10986)
at async JHt.execute (...extension.js:4768:808)
-
Closing the workspace folder (switching to an empty window) restores normal functionality — the AI connects and responds as expected.
Root Cause Analysis
The Roo Code extension relies on the ripgrep binary for workspace file indexing and search operations. When a folder is opened, the extension invokes ripgrep during initialization. If ripgrep is not found, the initialization fails and blocks the API connection pipeline.
Investigation confirms that:
-
rg.exe is not present in the Positron installation directory:
D:\Program Files\Positron\resources\app\node_modules\@vscode\ripgrep\ — does not exist
-
rg.exe is not present in the Roo Code extension directory:
C:\Users\<user>\.positron\extensions\rooveterinaryinc.roo-cline-3.54.0-universal\ — no ripgrep binary found
-
rg.exe is not in the system PATH.
-
The issue is specific to Positron 2026.08.1 — previous versions worked without requiring a separate ripgrep installation, suggesting that earlier releases either bundled ripgrep or the extension did not require it at the initialization stage.
Workaround
Manually install ripgrep and make it available:
Option A — Install ripgrep system-wide:
- Download from ripgrep releases.
- Add the directory containing
rg.exe to the system PATH.
- Restart Positron.
Option B — Copy an existing rg.exe to where the extension expects it:
mkdir "%USERPROFILE%\.positron\extensions\rooveterinaryinc.roo-cline-3.54.0-universal\node_modules\@vscode\ripgrep\bin"
copy <path-to-existing-rg.exe> "%USERPROFILE%\.positron\extensions\rooveterinaryinc.roo-cline-3.54.0-universal\node_modules\@vscode\ripgrep\bin\rg.exe"
Suggested Fix
Please consider one of the following:
- Bundle
@vscode/ripgrep with the Positron distribution (as VS Code does), ensuring that rg.exe is available at resources\app\node_modules\@vscode\ripgrep\bin\.
- Document the
ripgrep requirement for extensions that depend on it, so users are aware of the prerequisite.
- Coordinate with the Roo Code extension maintainers to provide a graceful fallback when
ripgrep is not found, rather than blocking the entire API connection.
Additional Context
- This is likely a regression introduced in the 2026.08.1 release.
- The issue affects all workspace folders, not just specific projects.
- Extensions that rely on
ripgrep for code search (e.g., any VS Code extension using @vscode/ripgrep) may be similarly affected.
- This issue is reproducible on a clean workspace (empty folder with no configuration files).
Thank you for your work on Positron — it's a fantastic tool for R and Python development!
Bug: Missing
ripgrepBinary in Positron 2026.08.1 Breaks Roo Code Extension When a Workspace Folder Is OpenSummary
After updating to Positron 2026.08.1, the Roo Code extension (v3.54.0) fails to connect to the AI API when any workspace folder is opened. The extension works correctly when no folder is opened (empty window). The root cause is that the
ripgrepbinary (rg.exe) is not bundled with this Positron release, and the Roo Code extension depends on it for file-system operations. This issue did not occur in prior Positron versions.Environment
D:\Program Files\Positron\rooveterinaryinc.roo-clinev3.54.0 (installed via Open VSX)@vscode/ripgrepnot found under Positron installation or extension directoriesSteps to Reproduce
D:\test).Expected Behavior
The Roo Code extension should connect to the configured AI API and respond normally, regardless of whether a workspace folder is open.
Actual Behavior
The Roo Code panel shows "Connecting to API..." indefinitely and never establishes a connection.
The extension's internal file-listing operation throws the following error:
Closing the workspace folder (switching to an empty window) restores normal functionality — the AI connects and responds as expected.
Root Cause Analysis
The Roo Code extension relies on the
ripgrepbinary for workspace file indexing and search operations. When a folder is opened, the extension invokesripgrepduring initialization. Ifripgrepis not found, the initialization fails and blocks the API connection pipeline.Investigation confirms that:
rg.exeis not present in the Positron installation directory:D:\Program Files\Positron\resources\app\node_modules\@vscode\ripgrep\— does not existrg.exeis not present in the Roo Code extension directory:C:\Users\<user>\.positron\extensions\rooveterinaryinc.roo-cline-3.54.0-universal\— noripgrepbinary foundrg.exeis not in the systemPATH.The issue is specific to Positron 2026.08.1 — previous versions worked without requiring a separate
ripgrepinstallation, suggesting that earlier releases either bundledripgrepor the extension did not require it at the initialization stage.Workaround
Manually install
ripgrepand make it available:Option A — Install
ripgrepsystem-wide:rg.exeto the systemPATH.Option B — Copy an existing
rg.exeto where the extension expects it:Suggested Fix
Please consider one of the following:
@vscode/ripgrepwith the Positron distribution (as VS Code does), ensuring thatrg.exeis available atresources\app\node_modules\@vscode\ripgrep\bin\.ripgreprequirement for extensions that depend on it, so users are aware of the prerequisite.ripgrepis not found, rather than blocking the entire API connection.Additional Context
ripgrepfor code search (e.g., any VS Code extension using@vscode/ripgrep) may be similarly affected.Thank you for your work on Positron — it's a fantastic tool for R and Python development!