gemini-cli - ✅(Solved) Fix "Ripgrep is not available. Falling back to GrepTool." message shown (only) in non-interactive mode [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#26193Fetched 2026-04-30 06:44:38
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
cross-referenced ×1labeled ×1

Fix Action

Fixed

PR fix notes

PR #26203: fix(core): quiet ripgrep fallback log

Description (problem / solution / changelog)

Summary

  • Move the ripgrep unavailable fallback message from warning to debug logging.
  • Keep GrepTool fallback behavior and ripgrep fallback telemetry unchanged.
  • Add regression coverage for both unavailable and erroring ripgrep detection paths.

Fixes #26193.

Tests

  • npm test --workspace @google/gemini-cli-core -- config.test.ts
  • npm run typecheck --workspace @google/gemini-cli-core
  • npx prettier --check packages/core/src/config/config.ts packages/core/src/config/config.test.ts

Changed files

  • packages/core/src/config/config.test.ts (modified, +24/-0)
  • packages/core/src/config/config.ts (modified, +3/-1)

Code Example

$ gemini --prompt "are you ready?"
Ripgrep is not available. Falling back to GrepTool.
I am ready. Please provide your instructions.

---

$ rg --version
ripgrep 13.0.0
-SIMD -AVX (compiled)

---

> /about
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                                                           │
About Gemini CLI│                                                                                                                                                           │
CLI Version                                           0.41.0-preview.0Git Commit                                            a5befa04f                                                                                           │
Model                                                 Auto (Gemini 3)Sandbox                                               no sandbox                                                                                          │
OS                                                    linux                                                                                               │
│                                                                                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
RAW_BUFFERClick to expand / collapse

What happened?

Observe:

$ gemini --prompt "are you ready?"
Ripgrep is not available. Falling back to GrepTool.
I am ready. Please provide your instructions.

The message Ripgrep is not available. Falling back to GrepTool. is, at best, confusing. It doesn't present any information as regards how to remedy the situation or silence the message.

For reference, the tool rg is installed on my Linux (ARM_64) system:

$ rg --version
ripgrep 13.0.0
-SIMD -AVX (compiled)

I don't have any explicit entry in my ~/.gemini/settings.json as regards tools.useRipgrep, so the default value of true applies, as confirmed by /settings:

│ ● Use Ripgrep true │ │ Use ripgrep for file content search instead of the fallback implementation. Provides faster search performance. │

I am using a "conventional" install of Gemini CLI:

$ sudo npm install -g @google/gemini-cli@preview

I.e., I am not using the SEA version, for which "Ripgrep binaries are now bundled into the Single Executable Application (SEA)".

What did you expect to happen?

  1. Given that I'm not using the SEA version of Gemini CLI (AFAIK, this is the only case in which the ripgrep binaries are bundled), the rg tool installed in my system should be used (if tools.useRipgrep is true.)
  2. If using my system's rg simply isn't supported, then tools.useRipgrep shouldn't have default true (except in the SEA case).
  3. The warning Ripgrep is not available. Falling back to GrepTool. shouldn't be so noisy. It would be better if it were shown only with gemini --debug --prompt ..., in my opinion.
  4. This warning should be treated consistently with non-interactive & interactive modes. Currently, it's shown for the former, but not the latter.

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
╭───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                                                           │
│ About Gemini CLI                                                                                                                                          │
│                                                                                                                                                           │
│ CLI Version                                           0.41.0-preview.0                                                                                    │
│ Git Commit                                            a5befa04f                                                                                           │
│ Model                                                 Auto (Gemini 3)                                                                                     │
│ Sandbox                                               no sandbox                                                                                          │
│ OS                                                    linux                                                                                               │
│                                                                                                                                                           │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
</details>

Login information

I'm logged in using my Google Account (AI Pro).

Anything else we need to know?

It would be helpful, IMO, to add more information to https://geminicli.com/docs/ regarding how to configure ripgrep for supported usage in Gemini CLI.

extent analysis

TL;DR

The issue can be resolved by configuring the tools.useRipgrep setting to use the system's rg tool or by using the SEA version of Gemini CLI.

Guidance

  • Verify that the rg tool is installed and available in the system's PATH.
  • Check the ~/.gemini/settings.json file to ensure that the tools.useRipgrep setting is set to true and that the rg tool is correctly configured.
  • Consider using the SEA version of Gemini CLI, which bundles the ripgrep binaries.
  • If using the non-SEA version, consider setting tools.useRipgrep to false to avoid the warning message.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue seems to be related to the configuration of the tools.useRipgrep setting and the availability of the rg tool in the system. The user is not using the SEA version of Gemini CLI, which bundles the ripgrep binaries.

Recommendation

Apply workaround: Set tools.useRipgrep to false in the ~/.gemini/settings.json file to avoid the warning message, or use the SEA version of Gemini CLI. This is because the non-SEA version does not seem to be using the system's rg tool correctly.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

gemini-cli - ✅(Solved) Fix "Ripgrep is not available. Falling back to GrepTool." message shown (only) in non-interactive mode [1 pull requests, 1 participants]