I have been using this for about a month and it’s a beast, mostly thanks to 2.5pro being SOTA and also how it leverages that huge 1M context window. Other tools either preemptively compress context or try to read files partially.
I have thrown very large codebases at this and it has been able to navigate and learn them effortlessly.
When I was using it in cursor recently, I found it would break imports in large python files. Claude never did this. Do you have any weird issues using Gemini? I’m excited to try the cli today
Ive seen it both in the Studio and via API, with various character replacements. It's weird, it's like its own dialect, the character usually corresponds to the word (or part od it) being replaced.
+1 I have not found Gemini 2.5 better than Claude's latest models -- different and better at some things, but not better in general; and in general I have found Gemini 2.5 Pro to be worse at dealing with large codebases despite its huge context window. So I too am quite curious about the workflow here.
the core idea is to not use up all of context for files but instead sessions go longer before becoming a useless pursuit ie. more turns possible with larger context window
i guess one core idea is to point it to an entrypoint or some part of code you are planning to touch. instead of asking it to load up every file etc. and then figure out the control flow.
I have thrown very large codebases at this and it has been able to navigate and learn them effortlessly.