When using the agent mode with Gemini 2.5 pro (with my own API key) the agent mode stops mid thinking or does not think itself. This model becomes unusable with this as it has been occurring more recently. Any fix regarding this.
Steps to Reproduce
add you api key, then use the 2.5 pro agent based on your api key, after some usage it stops mid thinking or stop thinking itself. sometimes the thinking gets through and it stop mid file updates.
Expected Behavior
The model should think properly and generate response and update the files
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Hey. Is everything okay with your internet? Maybe you’re experiencing network interruptions? Have you noticed this behavior when not using your API key?
@deanrie it is also breaking when using without the API key, it stops mid thinking or implementation phase, may be an issue at the google’s end. Read some reddit post’s of gemini breaking mid thinking or streaming.
added snapshot of it stopping mid thinking (without api key)
same issue. it starts generating then suddenly stops and get a message “We’re having trouble connecting to the model provider.”. it’s been going for a couple of days now
I havent found anything in google docs, that gemini 2.5 has 200k context and have a need to summarize context.
How about, if I pay you $20 month, you will let me actually use 1M context ?
Fair deal huh? Since I’m paying for Gemini’s api key usage
And you will stop cutting the thinking & context windows under the hood.
Gemini 2.5 in cursor is the dumbest entity I have ever interacted with.
I’m using online version of gemini to actually solve the issues cursor’s gemini does
Facing the same issue as well.When I use Gemini, it runs for a second and then immediately stops, repeating this cycle and making it unusable. Are there any solutions?
Can you guys confirm this with other coding IDEs, I just want to check if cursor is playing dirty here or not!
cause the first time this happened with me, cursor consumed the whole request token limit, causing Gemini API to start throttling requests.
Note: this is started to happen after cancelling my pro subscription (I thought to myself, Gemini free tier is more than enough for my daily uses anyway)
it works perfectly everywhere else and even within Cursor using the Gemini api key.
I’m pretty sure it’s not an issue from Google’s end as claimed here. It’s def some BS on Cursor’s end.
