Gemini 2.5 Pro made some big post-launch improvements for tool calling/agentic usage that made it go from “pulling teeth” to “almost as smooth as Claude” in Cline/Roo Code (which is saying something since Cline was originally built around Claude tool use specifically).

So the team at least seems to be aware of its shortcomings in that area and working to improve it with some success which I appreciate.

But you are correct that Gemini CLI still lags behind for whatever reason. It gets stuck in endless thought loops way too often for me, like maybe 1/15 tasks hits a thought loop burning API credits or it just never exits from the “Completing task, Verifying completion, Reviewing completion, Assessing completion status…” phase (watching the comical number of ways it rephrases it is pretty funny though).

Meanwhile I’ve only had maybe one loop over a period of a couple months using Gemini 2.5 Pro heavily in Roo Code with the most recent version so it seems like an issue with the CLI specifically.

▲

jjani 4 days ago | parent [-]

Even just a week ago Gemini was still outputting the same message twice almost every time in Cline, I doubt that has changed in the last week.

	▲	ewoodrich 4 days ago \| parent [-]
		Hmmm I haven't used for Cline for several months but in Roo I have made some (fairly minor) changes to my Roo Code code modes and have not experienced this at all. Especially that frequently, I use GPT 4.1 via my Copilot Pro plan and Gemini 2.5 Pro via OpenRouter as my daily drivers. That being said I have had found using Gemini through the AI Studio API much less reliable in Roo/Cline and I'm not sure how you are accessing it. I have auto approve turned on for most routine tasks and run Gemini for relatively long (by Cline/Roo standards) tasks unsupervised without issue, with the normal caveats of any LLM going off the deep end every now and then but haven't seen that more frequently with Gemini except in the first couple months 2.5 Pro was released.