Cursor throws error while connecting to Claude 4 Sonnet

Support Bug Reports
21

This project is moving so fast, it is like one is lucky to catch it working for a while :smiley:

By the time they fix a thing they break 3 others. By the nature of the AI wars and competition between these IDE apps, this will never change.

If it works for many users, even if not all, the company probably is ok with some bugs here and there.

22

Did you actually uninstall them, or did you just disable them in settings? I see a custom mode in the screenshot in OP which means they might have a different set of enabled MCP servers than the global set

23

Im also down to jump on a zoom call to debug

24

Also what mcp servers are you guys using, this would help me reproduce it much faster

25

I did removed them fully - I have ony github left

image
image1142×1000 49.8 KB

26

I tried all the steps but still it doesn’t work with MCP so what are the next steps ?

Request ID: 4c99cdc4-e139-4b61-9752-582bf6552969
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:},“isExpected”:false}
ConnectError: [unavailable] Error
at BWa.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4846:224431)
at wsr.S (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:495:17762)
at wsr.Q (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:495:17540)
at wsr.M (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:495:16628)
at wsr.L (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:495:15729)
at Wyt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:495:14521)
at we.B (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2398)
at we.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2617)
at Ynt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4833:10379)
at u.onmessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:7043:13881)

27

Same thing here since yesterday. Not using MCP. It just stopped connecting:
No matter what I do, it doesn’t work. Network diagnostics were fine.

image
image663×260 11.2 KB

28

I have just had to fully uninstall (I had to delete %APPDATA% to get this properly working) and downgraded to 1.3.9.

I wont be upgrading to the latest version again - waste of 2 hours trying to get things workin

Fix your release process Cursor - its abysmal

29

I am using 1.3.9 and still getting this issue. Let me try deleting %APPDATA%

30

Hey, please update to version 1.4.2, we fixed several bugs.

31

same issue with version 1.4.2

32

I was using this thing without success. I had to remove it completely nut just disable it but only a new chat fixed it after removing it.

33

I did managed to fix those “Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider.” errors by complete removal and reinstallation clean Cursor. When reinstalling I didn’t import anything from VSCode and just used clean vanilla cursor only.

Apart of removing cursor app from the Applications I have additionally remove associated files from your Library folder and possibly the ~/.cursor directory.

Here’s a more detailed breakdown:

  1. Quit Cursor:
    Ensure the Cursor application is not running by either right-clicking the icon in the dock and selecting “Quit”, or by going to Cursor in the menu bar and selecting “Quit Cursor”.
  2. Move to Trash:
    Open Finder, navigate to the Applications folder, and locate the Cursor application. Right-click on it and select “Move to Trash”.
  3. Remove Application Support Files:
    Open Finder, click “Go” in the menu bar, then select “Go to Folder…” and enter ~/Library.
    Open the Application Support folder and locate the cursor folder (and cursor nightly if you used a nightly build). Move these folders to the Trash.
  4. Remove Files from bin:
    Open Terminal.
    Navigate to the user local bin directory: cd /usr/local/bin.
    Delete the cursor file using: sudo rm cursor and enter your password.
    Confirm the file is deleted: ls.
  5. Remove Remaining Files:
    Navigate back to your home directory: cd ~.
    Check for and delete the .cursor folder using: rm -rf ~/.cursor.
    Check for and delete the cursor-tutor folder if it exists: rm -rf ~/.cursor-tutor.
    Navigate to the config folder: cd ~/.config.
    Check for and delete the cursor folder if it exists: rm -rf ~/.config/cursor.

After that install clean cursor without importing anything from other IDEs.

34

So it still doesn’t resolve the issue. Agent with Auto mode works fine but this issue occurs when using a Cursor Agent without Auto mode in conjunction with MCP tools.
Do we have any customer support from Cursor ?