gemini-cli - 💡(How to fix) Fix Stuck at thinking [3 comments, 4 participants]

Gemini CLI sometimes gets stuck on the “Thinking” state and does not return any response. This issue happens intermittently, so it does not occur every time, but when it does happen, the CLI continues processing for a long time without showing any output, error message, or timeout notification. The expected behavior is that Gemini CLI should either return a response within a reasonable amount of time or display a clear error message if the request fails or takes too long. However, the actual behavior is that it remains stuck on "Thinking," forcing the user to manually cancel the request, restart the CLI, or try again. This affects normal usage because it interrupts the workflow and makes the tool unreliable. Please investigate whether this issue is related to request timeout handling, network/API delays, or missing error feedback from the CLI. I expected Gemini CLI to process the prompt and return a response within a reasonable time. If the request failed or took too long, I expected it to show a clear error message or timeout notificati

TL;DR

Investigate and adjust the request timeout handling in the Gemini CLI to prevent it from getting stuck in the "Thinking" state.

Guidance

• Review the Gemini CLI configuration and code to identify the current request timeout settings and adjust them to a reasonable value to prevent long waits without feedback.
• Implement a timeout notification or error message to inform the user when a request takes too long, allowing them to cancel or retry the request.
• Consider adding logging or debugging statements to track the request processing time and identify potential bottlenecks or delays in the CLI or network/API interactions.
• Verify that the issue is not related to network or API delays by testing the CLI with different network conditions or API endpoints.

Notes

The root cause of the issue is uncertain, and further investigation is needed to determine whether it is related to request timeout handling, network/API delays, or missing error feedback from the CLI.

Recommendation

Apply a workaround by adjusting the request timeout settings and implementing a timeout notification or error message, as the root cause of the issue is unclear and may require further investigation.