gemini-cli - 💡(How to fix) Fix Add --verbose flag for detailed error output [1 participants]

When gemini-cli encounters errors (e.g., API failures, tool execution issues), the error output is minimal and doesn't help users debug root causes.

TL;DR

Adding a --verbose flag to the gemini-cli can help increase log detail and aid in debugging root causes of errors.

Guidance

• Implement the --verbose flag to display full stack traces, which can provide more insight into the source of the error.
• Include API request/response payloads in the verbose output, ensuring to redact sensitive keys to maintain security.
• Add logging for tool execution steps to help identify where issues occur during the process.
• Consider adding an example of how to use the --verbose flag in the documentation to facilitate its adoption by users.

Example

gemini-cli --verbose

This command would run the gemini-cli with increased log detail, helping users to debug issues more effectively.

Notes

The implementation details of the --verbose flag, such as how to redact sensitive information from API payloads, are not specified and may require additional development considerations.

Recommendation

Apply the workaround by implementing the --verbose flag, as it directly addresses the need for more detailed error output to aid in debugging and filing better bug reports.