Cursor requests failing

Support Bug Reports
,
1

Describe the Bug

Cursor MacOS app is rejecting all requests with We're having trouble connecting to the model provider. This might be temporary - please try again in a moment.

Steps to Reproduce

Any input to MacOS Cursor app encounters this issue.

Expected Behavior

Cursor responds.

Screenshots / Screen Recordings

Screenshot 2026-09-20 at 1.23.31 PM.png
Screenshot 2026-09-20 at 1.23.31 PM.png705×157 7.84 KB

Operating System

MacOS

Version Information

Version: 3.21.9
VS Code Extension API: 1.128.0
Commit: 9998796a6096ce83d83a9332bfe7473b985db750
Date: 2026-09-17T02:16:48.732Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.4.0

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

Request ID: c50e65ed-894d-4f1c-bc45-085a2c57d3ef

Additional Information

Log from the app:

Request ID: c50e65ed-894d-4f1c-bc45-085a2c57d3ef
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:false,“additionalInfo”:{“providerStatusCode”:“403”},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
NonRetriableError: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at K5f (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8151:216964)
at Kio (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8151:215473)
at _6f (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8152:14075)
at Object.classify (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8152:18296)
at p6f (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8152:6340)
at async sro.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8152:17603)
at async wle.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8252:31211)
at async X6o.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:17692:16857)
at async X6o.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:17692:38915)
at async cDe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8230:4412)

Does this stop you from using Cursor

Yes - Cursor is unusable

5

This problem is really unpredictable. I tried a workaround and it worked: send the same input in ask mode → (works) → send “go” in agent mode → (works)

This happens from time to time and is really bothersome.

6

This has been happening very frequently, even for pro subscribers :frowning:

7

I recently restarted the cursor, and it worked fine.

8

wiping processes and restarting doesn’t help, I’m getting this error constantly as an ultra subscriber - cursor is unusable because of that

settings → browser&network → “run diagnostics” gives a clean picture : all “success” - can’t post because the forum treats urls from the report as links)

This started after the upgrade of the macOS to 27 Golden Gate, not sure if this is connected

9

No changes so far - still unusable. Is there a way to get support?

10

image
image1328×762 47.9 KB

Fixed.

Cursor found and ran an Intel git binary somewhere, so the agent never started.
Must be a common issue after the macOS Golden Gate 27 upgrade, since no Intel binaries are supported anymore.

Still, it’s a shame Cursor doesn’t offer any sort of dedicated support for Ultra subscribers.

11

I’m having this same issue on one of my two machines under my Pro account. I’ve posted here: Cursor Agent gets stuck while exploring files and never generates a code change on macOS 27 - #19 by fabravo

20

Hey @Kannan_Mavila, thanks for the report and for sharing what worked!

Quick clarification on what you were seeing: despite the wording, this was not a connection problem. The model provider behind Auto declined those specific requests, and our app showed the generic “trouble connecting” message instead of saying so. I’ve flagged this for the team.

@crypt0grapher and @fabravo, what you two hit (the agent never starting after the macOS 27 upgrade) is a separate issue. Please follow along in the thread fabravo linked so we can keep this one focused.

21

I Am experiencing major connectivity issues with Cursor today. The editor is repeatedly Getting stuck at “Preparing…” and I keep getting timeout errors whenever I try to use the AI agent chat or code generation features.

Is anyone else experiencing this right now, or is there an official update from the dev team?

It is completely blocking my workflow, so any info on when a fix is expected or temporary workarounds would be greatly appreciated.