gemini-cli bug: timed-out ripgrep searches silently return wrong or empty results
Neal006 · ghdev · 2026-10-18
A gemini-cli issue reports that when RipGrepTool's grepsearch hits its 30s timeout, no error is raised: with 1–3 matches it returns "No matches found," with more it returns a truncated list — in both cases error is unset and the call counts as success, so the model never narrows or retries. Root cause: execStreaming treats the killed process as a normal exit, and the auto-context enrichment pass reuses the already-aborted timeout signal, returning an empty list that overwrites real matches. The reporter reproduced both cases with unit tests and proposes returning a timeout error or clearly flagging truncated results.
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23