(solved) Unable to Connect to Gemini-2.5 Models in Agent Mode

In Agent mode, the Gemini-2.5-pro-exp-03-25 and Gemini-2.5-pro MAX models do not work. I always get the following error message:
“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”

This issue has been occurring since yesterday, and I have not been able to use Agent mode at all. It is affecting my use of Cursor and impacting my work.

Steps to reproduce the issue:

  1. Select Agent mode.
  2. Choose one of the Gemini 2.5 models (either Gemini-2.5-pro-exp-03-25 or Gemini-2.5-pro MAX).

The error happens immediately.

macOS Information:

  • Version: macOS Sequoia 15.3.2
  • Computer Model: Mac Pro 2019
  • Processor: 3.6 GHz Intel Core i7 with 8 cores
  • Graphics Card: AMD Radeon RX 5700 XT 8 GB
  • Memory: 32 GB 2666 MHz DDR4
  • PCI Cards: 8 PCI card connectors

Cursor Information:

  • Version: 0.48.3
  • VSCode Version: 1.96.2
  • Commit: d0f26e6e7e022d8e024f7eb7d085-cadf3f1d4f20
  • Date: 2025-03-29T03:36:17.887Z (13 hours ago)
  • Electron: 34.3.4
  • Chromium: 132.0.6834.210
  • Node.js: 20.18.3
  • V8: 13.2.152.41-electron.0
  • OS: Darwin x64 24.3.0
3 Likes

+1 same [email protected]

same!

Hey, try disabling your MCP servers and see if that resolves the issue.

2 Likes

Hey deanrie, would you mind confirming how one does this on Cursor?

Hey, do you mean disabling MCP servers? If you haven’t added them, I don’t think you should have them.

Thank you for confirming, that is indeed what I was referring to.

Im curious why I might be having the issue then. I haven’t been able to use the Gemini 2.3 Pro max model. I have a Pro plan and have only used 37 of my monthly requests. Extremely frustrating to say the least, its driving me crazy lol. I tried reinstalling the application, all other models seem to work except for this one.

To use Max models, you need to enable the usage-based pricing option in your account settings.

I do have that setting enabled:

Do you have MCP servers enabled? If so, try disabling them, as this might be causing the error. I just checked, and it works for me. Also, try starting a new chat.

I did check this before as I saw this was a recommended solution in the past but found I currently have none enabled. I did create a new chat for this so I will see what comes from that. Thanks for this input

1 Like