What happened?
The Gemini CLI fails to utilize ripgrep (rg) on Linux even if it is available in the system's $PATH. It incorrectly reports "Ripgrep is not available. Falling back to GrepTool."
Root Cause: The current implementation in packages/core/src/tools/ripGrep.ts only looks for bundled binaries in internal vendor/ripgrep paths. If these bundled files are missing, the CLI ignores the global system binary.
What did you expect to happen?
The CLI should check for the system-wide ripgrep binary if the bundled version is not found, ensuring high-performance search is available.
Client information
Platform: Linux (Fedora)
Gemini CLI Version: 0.40.1
Login information
Google Account (OAuth personal)
Anything else we need to know?
I have already submitted a Pull Request fixing this issue here:
#26536
What happened?
The Gemini CLI fails to utilize ripgrep (rg) on Linux even if it is available in the system's $PATH. It incorrectly reports "Ripgrep is not available. Falling back to GrepTool."
Root Cause: The current implementation in packages/core/src/tools/ripGrep.ts only looks for bundled binaries in internal vendor/ripgrep paths. If these bundled files are missing, the CLI ignores the global system binary.
What did you expect to happen?
The CLI should check for the system-wide ripgrep binary if the bundled version is not found, ensuring high-performance search is available.
Client information
Platform: Linux (Fedora)
Gemini CLI Version: 0.40.1
Login information
Google Account (OAuth personal)
Anything else we need to know?
I have already submitted a Pull Request fixing this issue here:
#26536