Unable to Reach Model Provider Opus4.5, Sonnet4.5 and Gemini 3 Pro

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am using Opus 4.5 in Cursor and am consistently encountering an error that prevents the model from responding only when building a plan or running in Agent mode.

The model works correctly in Plan mode, but once I proceed to Build the plan or switch to Agent mode, the request fails and no response is returned.

Steps to Reproduce

Select Opus 4.5 as the active model

Enter a prompt and run it in Plan mode (works as expected)

Click Build Plan or switch to Agent mode

Observe that the request fails and the error ERROR_OPENAI – Unable to reach the model provider is returned

Expected Behavior

Opus 4.5 should respond successfully in all modes, including Plan, Build Plan, and Agent mode.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44 (user setup)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

opus4.5, sonnet 4.5 and Geminin 3 Pro

For AI issues: add Request ID with privacy disabled

Request ID: 3fa84d1b-92a7-4370-b727-644a7351b192
{“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”:,“planChoices”:},“isExpected”:false}

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

This kind of error is usually caused by an extension conflict or network settings. Let’s check a few things:

  1. Check extensions:
  • If you have Nx Console installed, uninstall it and restart Cursor (this is a known conflict)
  • Launch Cursor with a clean profile from the terminal: ‌cursor --user-data-dir=%TEMP%\cursor-test and try Agent mode
  1. Disable HTTP/2:
  • Press CTRL+, to open settings
  • Search for “HTTP/2”
  • Turn on “Disable HTTP/2”
  • Restart Cursor
  1. Collect diagnostics:
  • Cursor Settings > Network > Run Diagnostics, then share a screenshot of the results
  • Help > Toggle Developer Tools > Console, reproduce the error, and share a screenshot of the red errors
  • Copy 2 to 3 new Request IDs after the error (Chat menu > Copy Request ID)
  1. Extra info:
  • What’s your region or country?
  • Are you using a VPN or proxy?
  • What extensions do you have installed?

Similar cases:

Try the steps above and let me know what you find.

I followed these steps, but I still have the same issue. I don’t have the Nx installed as well
Also, I disabled HTTP/2.

I am from Turkey, and I don’t use vpn or proxy, and I don’t have any extensions installed. Everything was working fine from yesterday; this issue started today

  1. Change DNS:

  • Settings > Network > Change adapter options > connection properties > IPv4

  • Try Cloudflare DNS: 1.1.1.1 and 1.0.0.1

  • Or Quad9: 149.112.112.112 and 9.9.9.9

  • Restart Cursor

    1. Disable HTTP/2:
    • File > Preferences > Cursor Preferences > search for “HTTP” > “HTTP Compatibility Mode” > select HTTP/1.1

    • Restart Cursor

      Request ID: 93f75c79-d20d-4c66-ba57-fce4810f73dd
      {“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”:,“planChoices”:},“isExpected”:false}
      ConnectError: [unavailable] Error
      at szc.$endAiConnectTransportReportError (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12375:456006)
      at xBo._doInvokeHandler (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:22831)
      at xBo._invokeHandler (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:22573)
      at xBo._receiveRequest (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:21335)
      at xBo._receiveOneMessage (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:20152)
      at zLt.value (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:13027:18244)
      at Ee._deliver (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
      at Ee.fire (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
      at Tvt.fire (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12360:12156)
      at MessagePort. (vscode-file://vscode-app/c:/Users/User/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15027:18433)

@deanrie

@deanrie Just a kind reminder to follow up and see if there are any updates regarding this.

Thanks for the follow-up and detailed info.

I can see network diagnostics pass but the ConnectError: [unavailable] still happens specifically in Agent/Build mode. This pattern suggests the issue may be regional.

Could you please try one more thing:

  1. Test in Ask mode (not Agent) - does the same model work there?

  2. Try launching with a clean profile from terminal:

    cursor --user-data-dir=%TEMP%\cursor-test
    

    Then test Agent mode in this fresh instance.

  3. Share 2-3 new Request IDs from failed attempts after the clean profile test.

We’re tracking similar regional issues and the request IDs will help us investigate further.

1 Like