My tip: Move away from Google to an LLM that doesn't respond with "There was a problem getting a response" 90% of the time.
Are we getting billed for these? The billing is so very not transparent.
Copilot definitely bills you for all the errors.
Gemini CLI tips and tricks for agentic coding
51–60 of 152 posts
Re: Gemini CLI tips and tricks for agentic coding
#52Looking through this, I think a lot of these also apply to Google Antigravity which I assume just uses the same backend as the CLI and just UI wraps a lot of these commands (e.g. checkpointing).
Re: Gemini CLI tips and tricks for agentic coding
#53Earlier quoted context omitted.
I had to make a new API key. My old one got stuck with this error; it's on Google's end. New key resolved immediately.
and then loosing half a day setting up billing - with a limited virtual credit card so you have at least some cost control
For me, I had just set up a project and set billing to that. Making a second key and assigning the billing to that was instant; I got to reuse it.
I have sympathy for any others who did not get so lucky
Re: Gemini CLI tips and tricks for agentic coding
#54Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.
Well Opencode also completely replaced its TUI a few weeks ago too. BTW Gemini 3 via Copilot doesn't currently work in Opencode: https://github.com/sst/opencode/issues/4468
Copilot on Opencode is not good. It’s all over the place which is a shame because Copilot is one of the best values.
Re: Gemini CLI tips and tricks for agentic coding
#55Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.
YMMV I guess but it's my goto tool; fast and reliable results at least for my use cases
I'm constantly floored with how well claude-cli works and gemini-cli stumbled on something simple the first time I used it and Gemini's 3 Pro release availability was just bad.
Re: Gemini CLI tips and tricks for agentic coding
#56Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.
YMMV I guess but it's my goto tool; fast and reliable results at least for my use cases
Agreed. Been using Claude Code daily for the past year and Codex as a fall back when Claude gets stuck. Codex has two problems: it Windows support sucks and it's way to "mission driven" vs the collaborative Claude. Gemini CLI falls somewhere in the middle, has some seriously cool features (Ctrl+X to edit prompt in notepad) and it's web research capability is actually good.
Re: Gemini CLI tips and tricks for agentic coding
#57I am not doing any of this.
It becomes obsolete in literally weeks, and it also doesn't work 80% of the time. Like why write a mcp server for custom tasks when I don't know if the llm is going to reliably call it.
My rule for AI has been steadfast for months (years?) now. I write (myself, not AI because then I spend more time guiding the AI instead of thinking about the problem) documentation for myself (templates, checklist, etc.). I give ai a chance to one-shot it in seconds, if it can't, I am either review my documentation or I just do it manually.
Re: Gemini CLI tips and tricks for agentic coding
#58Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.
YMMV I guess but it's my goto tool; fast and reliable results at least for my use cases
I'm pretty sure we are in an apple vs android situation, where you give lifetime apple users an android phone, and after a day they report that android is horrid. In reality, they just aren't used to how stuff is done on android.
I think many devs are just in tune with the "nature" of Claude, and run aground easier when trying to use gemini or Chatgpt. This also explains why we get these perplexing mixed signals from different devs.
Re: Gemini CLI tips and tricks for agentic coding
#59Kinda useful, especially tip 15 and tip 26.
There needs to be a lot more focus on the observability and showing users what is happening underneath the hood (especially wrt costs and context management for non-power users).
A useful feature Cursor has that Antigravity doesn't is the context wheel that increases as you reach the context window limit (but don't get me started on the blackbox that is Cursor pricing).
Re: Gemini CLI tips and tricks for agentic coding
#60Earlier quoted context omitted.
YMMV I guess but it's my goto tool; fast and reliable results at least for my use cases
I'm pretty sure we are in an apple vs android situation, where you give lifetime apple users an android phone, and after a day they report that android is horrid . In reality, they just aren't used to how stuff is done on android. I think many devs are just in tune with the "nature" of Claude, and run aground easier when trying to use gemini or Chatgpt. This also explains why we get these perplexing mixed signals fro…
There are some clear objective signals that aren’t just user preference. I shelled out the $250 for Gemini’s top tier and am profoundly disappointed. I had forgotten that loops were still a thing. I’ve hit this multiple times in Gemini CLI, and in different projects. It gets stuck in a loop (as in the exact same, usually nonsense, message over and over) and the automated loop detection stops the whole operation. It also stops in the middle of an operation very frequently. I don’t hit either of these in Claude Code or Codex.
There certainly is some user preference, but the deal breakers are flat out shortcomings that other tools solved (in AI terms) long ago. I haven’t dealt with agent loops since March with any other tool.