Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gemini CLI tips and tricks for agentic coding

github.com

Post reply on HN
Print view View original

21–30 of 152 posts

Re: Gemini CLI tips and tricks for agentic coding

#21

Post by mhitza »

knollimar wrote: post #11
3578987532688 wrote: post #4

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.

Would be nice to have an official confirmation. Once token get back to the user those are likely already counted.

Sucks when the LLM goes on a rant only to stop because of hardcoded safeguards, or what I encounter often enough with Copilot: it generates some code, notices it's part of existing public code and cancels the entire response. But that still counts towards my usage.

Re: Gemini CLI tips and tricks for agentic coding

#23

Post by knollimar »

tarruda wrote: post #12
3578987532688 wrote: post #4

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.

I had a terrible first impression with Gemini CLI a few months ago when it was released because of the constant 409 errors. With Gemini 3 release I decided to give it another go, and now the error changed to: "You've reached the daily limit with this model", even though I have an API key with billing set up. It wouldn't let me even try Gemini 3 and even after switching to Gemini 2.5 it would still throw this error af…

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.

Re: Gemini CLI tips and tricks for agentic coding

#28

Post by tekacs »

SamDc73 wrote: post #18

A lot of times Gemini models will get stuck in a loop of errors in a lot of times it fails to edit/read or other simple function calling it's really really terrible at agentic stuff

Not so much with Gemini 3 Pro (which came out a few days ago)... to the point that the loop detection that they built into gemini-cli (to fight that) almost always over-detects, thinking that Gemini 3 Pro is looping when it in fact isn't. Haven't had it fail at tool calls either.

Re: Gemini CLI tips and tricks for agentic coding

#30

Post by OsrsNeedsf2P »

knollimar wrote: post #11
3578987532688 wrote: post #4

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.

My experience working in FAANG.. Nobody knows
Post reply on HN