Issue with Cursor AI Connection

[mdeviatov]

Describe the Bug

Hi!
I’m experiencing an issue with Cursor AI, where I receive the following error message:

“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”

Request ID: da2a46e5-68d4-4947-a97c-877a04359851.

I’ve already tried restarting the application and checking my internet connection, but the issue persists. I’d greatly appreciate your assistance in resolving this as soon as possible, as the tool is important for my work.

Please let me know if you need any additional details (e.g., app version or other information) to help diagnose the problem. Thank you in advance for your support!

Best regards

Steps to Reproduce

The issue has been persistent for the past 2 hours. It occurs with every request made to the agent in Cursor AI, resulting in the error message: “We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.” The problem persists despite restarting the application and verifying a stable internet connection.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:53:59.659Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, which model are you using? Have you also tried creating a new chat?

[thoainguyen]

I have same issue today even with Auto.

[sunnydsouza]

Yes, facing same issue specifically with claude 4 right now

Actually worse, with usage request, all of these failed attempts were counted in the 500 requests (which was always the case, they say “not charged”, but ALWAYS charged)

[deanrie]

Hey, does it happen in new chats?

[sunnydsouza]

It worked in new chats, but i did observe a pattern if you start a chat with o3, create a plan and then use claude 4 sonnet, then you run into this issue.
Atleast happened twice today
Whats worse the errors are counted towards my usage, for which you havent responded above. I wasted atleast 15 requests trying to retry thinking its a connection error.

[deanrie]

Thanks for the detailed information. We’ll investigate it.