Gemini CLI
Cryptic access denial without explanation or recourse
7Developers experience unexplained access rejections (e.g., "not allowed" to use Gemini Pro with CLI) despite having valid API keys and paying for the service. No reason is given and there is no documented recourse, creating frustration and blocking workflows.
Tool use errors and repeated failure patterns
7Gemini CLI frequently encounters tool use errors when applying changes to files. Once errors begin, the model repeats the same errors across the session without adaptation, making it stuck in failure loops that require manual intervention to resolve.
Lack of planning mode and uncontrolled automated changes
7Gemini CLI lacks a planning mode or safeguard to prevent the model from making changes before user approval. Users cannot programmatically control when changes are applied, forcing them to continuously intervene to prevent unintended modifications.
Poor performance and slow startup of Gemini CLI
7Gemini CLI has significant performance issues in standard CLI mode, with long startup times after install/update and 2-second delays between responses. While ACP protocol mode (Zed/Neovim integration) is snappy, the native CLI experience is so poor that developers consider switching to alternatives.
Domain-specific language support and excessive prompt engineering required
6Working with domain-specific languages like Terraform requires excessive prompt engineering with Gemini CLI. The model struggles with DSL semantics, necessitating detailed and repetitive prompt tweaking to achieve correct results.
Associated GitHub Repository Issues with Minimal Communication
6Multiple Google-maintained GitHub repositories (Gemini CLI, Python GenAI) have had unresolved issues for 2+ weeks with minimal communication. Developers report lack of transparency on resolution timelines.
Excessive chat spam and scrollback issues from file content leakage
6Gemini CLI unintentionally outputs file contents and changed file versions before applying edits, creating excessive chat spam. This causes severe scrollback/buffer bloat, especially on window resize, making the interface unusable and obscuring meaningful interactions.
Coarse-grained tool permissions requiring excessive babysitting
5Gemini CLI lacks support for tool subcommands (e.g., git status vs git rm), forcing developers to grant all-or-nothing permissions for entire binaries like `git`, `gh`, `vercel`, or `supabase`. Users must constantly babysit permission requests instead of setting granular policies.
Missing session persistence in Gemini CLI
4Gemini CLI does not automatically save sessions, requiring users to manually manage conversation state. This reduces continuity and forces workarounds to maintain context across CLI invocations.