Where do you face the biggest challenges with Gemini CLI?

|--| |Where do you face the biggest challenges with Gemini CLI? A) Authentication: The setup process is painful, confusing, or not well-documented. 1% B) Code Quality & Reliability: The generated code is inconsistent, not production-ready, or requires a lot of debugging. 38% C) Workflow Friction: Reviewing changes is difficult, and the agent doesn't always create a plan before starting. 21% D) Difficulties with domain-specific languages (e.g., Terraform) and excessive prompt engineering. 5% E) Quota issues: I run out of Quota before I’m able to make meaningful progress. 27% F) Something Else (please leave a comment with details). 5% 70 votes ·| … ### wiiiimm Aug 30, 2025 - Gemini CLI isn't the problem right now. The bottleneck is the model's ability to understand and debug code properly. Problem E - "I ran out of Quota before I'm able to make meaningful progress" - usually happens when I try to set Gemini CLI on a debugging task only to watch it go in circles for close to 30 minutes and burnt through a lot of quotas. It also manifest as Problem B and D as well. 0 replies … ... On first impressions, the Gemini cli takes a long time to start after the first install or after an update. That made a bad first impressions. After replying to every message, it waits for 2 seconds, doing nothing, which is annoying and a waste of developer time. I ended up not using Gemini cli much. I did use Gemini-2.5-Pro in Roo Code. It likes to write a lot of comments, which is good for learning something new, but it's not good for agentic coding. You can easily tell the code was written by AI because a normal dev doesn't write so many comments … ### BobTB Aug 30, 2025 ... The main problem preventing normal usage are insanely **low quotas for Gemini PRO subscribers**! Its incredibly frustrating to get blocked after 1-3M tokens sent and not even 10 prompts. (the output tokens were 7k only). Useless. Why are we paying for the PRO subscription if we can not use this in the Gemini CLI and are treated as the free users or worse. … ### boilthesea Aug 31, 2025 - Tool use errors, often runs into trouble applying changes to a file, sometimes it adapts better than others but once it starts having issues it tends to repeat them as is the case with gemini api + other tools. Was hoping that integrating the model with the software would work better and I suppose it does, but it's still a problem. Just had repeated errors in a session today. … ### bpavuk Aug 31, 2025 ... B, C, and performance. Neovim is snappy, LSPs I use are snappy, and Gemini CLI is snappy... only if you use it in ACP mode (that protocol that integrates with Zed and Neovim code-companion). but the performance of CLI interface itself is so awful that I want to fork Rust-based Codex CLI and just add Gemini model support, although GPT-5-mini is not that expensive and works better than Gemini 2.5 Pro, so I might switch. ... > A) Authentication: The setup process is painful, confusing, or not well-documented. Here''s a PR to fix painful authentication process when using API key: #6994 0 replies - - - - … 1. Does not automatically save sessions (looks like this will be addressed soon) 2. Lack of planning mode or anything to programmatically prevent the model from making changes before I'm ready. Yelling at it only works so well 3. Scrollback/chat spam. Especially because Gemini seems to be accidentally spitting out the contents of files it reads, or spitting out a changed version of a file before making the edit. This all adds up to it getting stuck scrolling through the buffer, especially when resizing the window. Core problem is the scrollback, the chat spam contributes to it. … 5. Poor (but improving) management of allowed tool calls. Gemini doesn't support tool subcommands. Instead of always allowing `git status` and always requiring permission for `git rm, git push, git switch, etc.` you have to babysit each call because you can only give it full permissions for `git` binary itself. Same problem with `gh` or `vercel` or `supabase`.