gemini-cli - 💡(How to fix) Fix CLI stuck on "Thinking..." state even after successful Google OAuth re-authentication [1 comments, 2 participants]

The Gemini CLI remains in a permanent "Thinking..." state whenever any command is issued. The CLI does not return an error, timeout, or any output, even after waiting for an extended period. There are no clear error logs being printed. Is there a way to enable a more detailed debug/verbose mode to see where the handshake is failing? The CLI should process the prompt and return a response or a specific error message (e.g., Quota exceeded or Network error).

TL;DR

Enable a more detailed debug/verbose mode to diagnose the handshake failure causing the Gemini CLI to hang indefinitely.

Guidance

• Investigate the possibility of enabling a debug or verbose mode for the Gemini CLI to gather more detailed logs, which could help identify where the handshake is failing.
• Review the Gemini CLI documentation or help commands (e.g., gemini --help) to see if there are any options for increasing log verbosity or enabling debug output.
• Consider checking the system's network configuration and firewall settings to ensure they are not interfering with the CLI's ability to connect to the Generative Language API.
• If possible, test the Gemini CLI on a different network or environment to isolate if the issue is specific to the current setup.

Example

No specific code snippet can be provided without more information on the Gemini CLI's internal workings or APIs. However, an example of how to enable verbose mode in a CLI tool might look like: gemini --verbose or gemini -v, though this is speculative and depends on the actual CLI options available.

Notes

The solution is limited by the lack of detailed error logs or specific information about the Gemini CLI's internal mechanics. Enabling a debug mode, if available, would be a crucial step in diagnosing the issue further.

Recommendation

Apply workaround: Enable debug/verbose mode if possible, to gather more information about the failure point. This approach is chosen because it directly addresses the need for more detailed diagnostics without making assumptions about the underlying cause or requiring changes to the environment or CLI version.