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

31–40 of 152 posts

Re: Gemini CLI tips and tricks for agentic coding

#31

Post by dnw »

randomsofr wrote: post #29
lvl155 wrote: post #25

Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.

what happened with Codex? Did they rebuild it?

I too am curious. My daily driver has been Claude Code CLI since April. I just started using Codex CLI and there are lot of gaps--the most annoying being permissions don't seem to stick. I am so used to plan mode in Claude Code CLI and really miss that in Codex.

Re: Gemini CLI tips and tricks for agentic coding

#32

Post by qsort »

randomsofr wrote: post #29
lvl155 wrote: post #25

Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.

what happened with Codex? Did they rebuild it?

The model needs to be trained to use the harness. Sonnet 4.5 and gpt-5.1-codex-max are "weaker" models in abstract, but you can get much more mileage out of them due to post-training.

Re: Gemini CLI tips and tricks for agentic coding

#33

Post by SamDc73 »

tekacs wrote: post #28
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.

Tried in V0, it always gets into an infinite loop

will give the CLI another shot

Re: Gemini CLI tips and tricks for agentic coding

#34

Post by bigcloud1299 »

formerly_proven wrote: post #19
ayewo wrote: post #17

Earlier quoted context omitted.

> Set me back 2 weeks of work. How did this happen? Did you let the agent loose without first creating its own git worktree?

tfw people are running agents outside containers

Apologies. I meant branch. I nuked the branch. But set me back a lot of time as I thought it may be few things here and there.

Re: Gemini CLI tips and tricks for agentic coding

#35

Post by bigcloud1299 »

formerly_proven wrote: post #19
ayewo wrote: post #17

Earlier quoted context omitted.

> Set me back 2 weeks of work. How did this happen? Did you let the agent loose without first creating its own git worktree?

tfw people are running agents outside containers

Yeah this something I need to get to.

Re: Gemini CLI tips and tricks for agentic coding

#38

Post by voodooEntity »

I really tried to get gemini to work properly in Agent mode. Tho it way to often wen't crazy, started rewriting files empty, commenting like "here you could implement the requested function" and many more stuff including running into permanent printing loops of stuff like "I've done that. What's next on the debugger? Okay, I've done that. What's next on the with? Okay, I've done that. What's next on the delete? Okay, I've done that. What's next on the in? Okay, I've done that. What's next on the instanceof? Okay, I've done that. What's next on the typeof? Okay, I've done that. What's next on the void? Okay, I've done that. What's next on the true? Okay, I've done that. What's next on the false? Okay, I've done that. What's next on the null? Okay, I've done that. What's next on the undefined? Okay, I've done that..." which went on for like 1hour (yes i waited to see how long it takes for them to cut it).

Its just really good yet.

I recently tried IntelliJs Junie and i have to say it works rather well.

I mean at the end of the day all of them need a human in the loop and the result is just as good as your prompt, tho with Junie i at least most of the time got something of a result, while with gemini 50% would have been a good rate.

Finally: Still dont see agentic coding for production stages - its just not there yet in terms of quality. For research and fun? Why not.

Re: Gemini CLI tips and tricks for agentic coding

#39

Post by neural_thing »

vidarh wrote: post #7
albert_e wrote: post #3

A lot it seems to mirror syntax of Claude Code Integration with Google Docs/Spreadsheets/Drive seems interesting but it seems to be via MCP so nothing exclusive/native to Gemini CLI I presume?

There seems to be an awful many "could" and "might" in that part. Given how awfully limited the Gemini integration inside Google Docs is, it's an area that's just made me feel Google is executing really slowly on this.

I've built a document editor that has AI properly integrated - provides feedback in "Track Changes" mode and actually gives good writing advice. If you've been looking for something like this - https://owleditor.com

Re: Gemini CLI tips and tricks for agentic coding

#40

Post by oblio »

lvl155 wrote: post #25

Gemini CLI sucks. Just use Opencode if you have to use Gemini. They need to rebuild the CLI just as OAI did with Codex.

> To use OpenCode, you’ll need:

> A modern terminal emulator like:

> WezTerm, cross-platform

> Alacritty, cross-platform

> Ghostty, Linux and macOS

> Kitty, Linux and macOS

What's wrong with any terminal? Are those performance gains that important when handling a TUI? :-(

Edit:

Also, I don't see Gemini listed here:

https://opencode.ai/docs/providers/

Only Google Vertex AI (?): https://opencode.ai/docs/providers/#google-vertex-ai

Edit 2:

Ah, Gemini is the model and Google Vertex AI is like AWS Bedrock, it's the Google service actually serving Gemini. I wonder if Gemini can be used from OpenCode when made available through a Google Workspace subscription...

Post reply on HN