[KenoFischer]

Tried it out.

1. First authentication didn't work on my headless system, because it wants an oauth redirect to localhost - sigh.

2. Next, WebFetch isn't able to navigate github, so I had to manually dig out some references for it.

3. About 2 mins in, I just got ``` ℹ Rate limiting detected. Automatically switching from gemini-2.5-pro to gemini-2.5-flash for faster responses for the remainder of this session. ``` in a loop with no more progress.

I understand the tool is new, so not drawing too many conclusions from this yet, but it does seem like it was rushed out a bit.

[dylancm]

Similar. Yesterday things seemed to be going okay. It was trucking along, making code changes.

Then I hit the rate limit. - Fine, no worries, it'll be interesting to see if the quality changes.

Then it starts getting stuck and taking forever to complete anything. So I shut it down for the day.

Today, I start it back up and ask it to pickup where it left off and it starts spinning. I forget about it and come back 7.5 hours later and it' still spinning. When I kill it it said: 1 Turn, 90k input tokens, 6.5 hours of API time... WTH?

And now I'm just totally rate limited - `status: 429, statusText: 'Too Many Requests'` - every time. Also, I can't find any kind of usage data anywhere!

[hvtuananh]

I got the same experience. I ran `gemini --debug` and it spit out the authentication URL at least. However I got the same `Rate limiting detected` for a simple refactoring task in a repo with 2 python files after a few minutes.

[gooob]

not working for me either. getting "too many requests". my own CLI tool i wrote for gemini last week works better lol. maybe i have something configured wrong? though that really shouldn't be the case. my api key env var is correct.