Hey I think this got accidentally fixed. Sweet!
gemini-2.5-pro-preview-05-06 released, as you’ve undoubtedly seen, and so far on max mode I am now no longer hitting rate limits. I hope it’s using my key.
never mind i hit a rate limit, even though i’m tier 2 on the api key.
With the release of gemini‑2.5‑pro‑preview‑05‑06, the demand to call the Gemini API directly from Cursor has only increased.
In Pro‑Max mode, users can’t choose—or even confirm—which exact model version is being called, and that’s a serious shortcoming.
I hope this gets fixed soon. Staying in step with the rapid model rollout is hard, but it’s precisely what gives Cursor its value; if we can’t tap into the newest models efficiently, who’s going to want yet another subscription?
1 Like
It looks like we’re all going to have to deal with this issue for a while longer. It’s probably just one line of code that needs to be changed for gemini-2.5-pro-max to point to the model gemini-2.5-pro-preview-05-06 and this post is automatically gonna close in 2 weeks so well be back to square one then. im still confused as to why cursor would want to use the exp model, wouldnt it make sense to use a stable model?
1 Like
I’m gonna get a couple of boys to start digging in here and get to the bottom of this so I can help @danperks fix the issue this git should be a stepping stone GitHub - rinadelph/CursorPlus: Enables source file where you can edit and improve your own cursor ide
This might be related. Check your GCP console which model was actually used.
Thanks for sharing the link.
I dug into the files and tried to identify where Cursor actually calls Gemini, but I couldn’t track it down with my skill.
In workbench.desktop.main.js I can only see codes related to gemini‑2.0 and gemini‑1.5; so far I haven’t located any call to gemini‑2.5. (Maybe it needs to add a new if-branch in the common handler for models whose names start with “gemini‑”.)
Ideally the Cursor team will add support for the preview model, but if we can’t get what we want, perhaps we should build it ourselves.
If you manage to switch the endpoint to gemini‑2.5, I’d really appreciate it if you let me know. I’m going to keep digging into this a bit more as well.
yea same here. i wasn’t able to find anything regarding 2.5 it might be in another file i didn’t want to waste time on it as i thought this would of been fixed by now.
@danperks is there any update on this? We’re sitting on a boat-load of Gemini credits that we’re unable to use in Cursor because of this issue.
Good news - I believe both models should now show seperalty in Cursor, so should be much better to use with an API key and MAX mode!
1 Like
I see it. Thanks @danperks and team!
I wasn’t sure what Dan meant about both models needing to show separately. What model should I be using with my own key if I want to access the actual gemini-2.5-pro-preview-05-06 using Max Mode? Also, what model do I need to enter in Cursor?
Here’s a screenshot of what I see under the model selection when my API keys are enabled.
I see it now. I just got the notification to update cursor to 0.50.4