gemini-cli - 💡(How to fix) Fix [Bug]: CLI stalls silently on startup in headless/remote environments (keychain access failure) [1 comments, 2 participants]

TL;DR

Setting the GEMINI_FORCE_FILE_STORAGE environment variable to true may resolve the freeze issue when running the gemini CLI in a headless terminal environment.

Guidance

• The likely cause of the issue is the CLI's attempt to access the native OS secure keychain, which is unavailable in standard remote workflows.
• To verify, try running the gemini CLI with the GEMINI_FORCE_FILE_STORAGE=true environment variable set and check if the application starts normally.
• To mitigate the issue, set the GEMINI_FORCE_FILE_STORAGE environment variable to true before running the gemini CLI, as shown in the provided workaround.
• This workaround may have implications for the application's security and storage mechanisms, so it's essential to understand the trade-offs before implementing it.

Example

export GEMINI_FORCE_FILE_STORAGE=true
gemini

Notes

The provided workaround may not be a permanent solution and might have security implications. It's crucial to investigate the root cause of the issue and consider alternative solutions that balance security and functionality.

Recommendation

Apply the workaround by setting GEMINI_FORCE_FILE_STORAGE=true to resolve the immediate issue, as it is a straightforward and effective solution to the problem described.