GoogleSearch tool hangs indefinitely in Thinking state without timeout

Finding: In external reports on google-gemini/gemini-cli, the built-in GoogleSearch (google_web_search) tool can leave the CLI in a Thinking state for a very long time with no upper bound on tool execution. The original report cites CLI 0.61.0 on win32 (no sandbox, Google sign-in, Code Assist Standard) and describes a hang of 31+ minutes that only Esc ended; it says no error or timeout occurred (https://github.com/google-gemini/gemini-cli/issues/29594). The reporter's view is that the tool promise stays unresolved without an AbortController timeout. That is the reporter's interpretation, not a maintainer-confirmed cause. A second reporter saw the same on 0.60.0 on Linux in ACP mode (gemini --acp). A metadata-only trace showed five web search calls in one turn taking 42s, 248s, 265s, 853s and 102s, while local grep_search and read_file calls took under 50 ms each. The turn lasted about 28 minutes. The debug log showed one 503 inside WebSearchToolInvocation.execute followed by retryWithBackoff retries (https://github.com/google-gemini/gemini-cli/issues/29594#issuecomment-5962749499). This suggests some long calls are slow server responses plus backoff retries rather than a permanent hang. That is a hypothesis from one report, not confirmed. A later commenter restates this retry-accumulation hypothesis and says PR #29608 appears to add a timeout around web search and WebFetch (https://github.com/google-gemini/gemini-cli/issues/29594#issuecomment-6060781441). The supplied sources do not show that PR's content, merge, commit or release, so fix status is unverified. Do not treat the issue as fixed in any release. Workarounds reported: Esc cancels the hung call. One ACP client cancels the whole turn after a single tool call exceeds 10 minutes, but ACP cannot cancel one tool call, so the agent loses the turn instead of receiving a recoverable tool error. Diagnostic hint, source-backed: if only web search calls are slow while local tools are fast, check the debug log for 503 and retryWithBackoff entries around WebSearchToolInvocation.execute. Limitations: these are external reports; KFA did not reproduce them. No maintainer response or confirmed cause appears in the supplied timeline, and comments may be incomplete.