Unable to Reach Model Provider for All Models Except Composer1

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

All local AI models except Composer1 (nice!) fail to run. Composer1 works normally, but every other model either fails to start or errors out immediately. The issue persists across restarts, cache resets, different networks, and protocol changes.

Steps to Reproduce

  1. Open Cursor
  2. Select any local model other than Composer1
  3. Run a prompt
  4. Error appears: “Unable to reach the model provider”

Troubleshooting steps I already tried:

killall Cursor

rm -rf ~/Library/Application\ Support/Cursor/logs
rm -rf ~/Library/Application\ Support/Cursor/CachedData
rm -rf ~/Library/Application\ Support/Cursor/CachedExtensions
rm -rf ~/Library/Application\ Support/Cursor/CachedExtensionVSIXs

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Other things I tried:

  • Switched HTTP/2.0 to HTTP/1.1
  • Tried different networks (Wi-Fi, hotspot)
  • With VPN and without VPN

The issue persists across all of these attempts and models.

I am on macOS Tahoe 26.1

This is issue first appear mid last week.

Expected Behavior

All local models should load and respond successfully.
Currently, only Composer1 works. Every other model fails with the “Unable to reach the model provider” error.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.46
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

For AI issues: which model did you use?

All models but Composer in all modes locally. Background agent is working.

For AI issues: add Request ID with privacy disabled

Privacy mode is enabled by company policy.

Request ID: 2ed47036-55e4-4ce2-b7b0-d6a2d42d9aa1

{"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 jZc.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:19194)
    at _Pt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:17286)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
    at tpt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8977:18439)

Does this stop you from using Cursor

Yes - Cursor is unusable

Unable to reach Opus 4.5 (base and thinking)
Opus 4.5 complaing Cursor keeps timing out
Unable to reach model provider. Max dimensions:2000?
2.1.48 Update: Persistent "Unable to reach model provider" & Chat History Loss
Unable to reach model provider Issue
Cannot submit to agent
Can only use Composer 1 with Perplexity MCP server
Planning next moves stuck
2

Hey, thanks for the report. The error “Unable to reach the model provider” looks like a routing/provider issue. It’s telling that Composer 1 works, while all other models fail.

To figure this out, please share:

  • Cursor Settings > Network > Run Diagnostics > screenshot of the full result
  • Help > Toggle Developer Tools > Console > errors/statuses at the moment of failure (screenshot or copy)
  • Which exact models you tested (Claude Sonnet 4/4.5, GPT-4/5, Gemini) and what mode (Ask, Agent)?
  • Create a new chat with the non-working model > result?
  • 2-3 recent Request IDs for the failed requests
  • Result on a mobile hotspot (specify country/provider)

Please share this data, and if needed, I’ll pass it to the team.

3

Hey Dean,

Thanks for your help!

Network screenshot (using Nordlayer):

image
image1678×4563 640 KB

Network screenshot (using WIFI):

image
image1628×5064 720 KB

Network screenshot (using Mobile):

image
image1632×4490 633 KB

On mobile (opus 4.5):

(t-mobile - US number / account)

Request ID: 063c19a6-758d-41ab-a9cf-49760a35e82a
{"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 jZc.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:19194)
    at _Pt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:17286)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
    at tpt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8977:18439)

On mobile (sonnet 4.5):

Request ID: 7f66d0af-7de8-4996-bf32-39cc9da0d03d
{"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 jZc.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:19194)
    at _Pt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:17286)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
    at tpt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8977:18439)

On mobile (Gemini 3 Pro):

Request ID: b75e46e4-242f-4235-8845-2c0ad676f710
{"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 jZc.$endAiConnectTransportReportError (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:19194)
    at _Pt.value (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6948:17286)
    at _e._deliver (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
    at _e.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
    at tpt.fire (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8977:18439)

I tested all modes (agent, plan, ask) with each model and each internet connection.

Console logs:

workbench.desktop.main.js:7187 [AgentService] Error running agent: ConnectError: [unavailable] Error
    at jZc.$endAiConnectTransportReportError (workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (workbench.desktop.main.js:6948:19194)
    at _Pt.value (workbench.desktop.main.js:6948:17286)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at tpt.fire (workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (workbench.desktop.main.js:8977:18439)
workbench.desktop.main.js:6996 [AiService] streamResponse ConnectError: [unavailable] Error
    at jZc.$endAiConnectTransportReportError (workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (workbench.desktop.main.js:6948:19194)
    at _Pt.value (workbench.desktop.main.js:6948:17286)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at tpt.fire (workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (workbench.desktop.main.js:8977:18439)
workbench.desktop.main.js:6995 [transport] Stream response error ConnectError: [unavailable] Error
    at jZc.$endAiConnectTransportReportError (workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (workbench.desktop.main.js:6948:19194)
    at _Pt.value (workbench.desktop.main.js:6948:17286)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at tpt.fire (workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (workbench.desktop.main.js:8977:18439) 
{arch: 'arm64', platform: 'darwin', channel: 'stable', client_version: '2.1.46', generationUUID: 'de705ce0-1cf3-4d82-8c88-6bb5fdef1094', …}
workbench.desktop.main.js:6995 [transport] Automatic bug report submitted for unexpected connection error 
{arch: 'arm64', platform: 'darwin', channel: 'stable', client_version: '2.1.46', requestId: 'de705ce0-1cf3-4d82-8c88-6bb5fdef1094', …}
workbench.desktop.main.js:4065 [composer] Error in AI response: {"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 jZc.$endAiConnectTransportReportError (workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (workbench.desktop.main.js:6948:19194)
    at _Pt.value (workbench.desktop.main.js:6948:17286)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at tpt.fire (workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (workbench.desktop.main.js:8977:18439)
workbench.desktop.main.js:6995 [composer] Error in AI response ConnectError: [unavailable] Error
    at jZc.$endAiConnectTransportReportError (workbench.desktop.main.js:6331:408762)
    at dLo._doInvokeHandler (workbench.desktop.main.js:6948:21873)
    at dLo._invokeHandler (workbench.desktop.main.js:6948:21615)
    at dLo._receiveRequest (workbench.desktop.main.js:6948:20377)
    at dLo._receiveOneMessage (workbench.desktop.main.js:6948:19194)
    at _Pt.value (workbench.desktop.main.js:6948:17286)
    at _e._deliver (workbench.desktop.main.js:49:2962)
    at _e.fire (workbench.desktop.main.js:49:3283)
    at tpt.fire (workbench.desktop.main.js:6316:12156)
    at MessagePort.<anonymous> (workbench.desktop.main.js:8977:18439) 
{arch: 'arm64', platform: 'darwin', channel: 'stable', client_version: '2.1.46', requestId: 'de705ce0-1cf3-4d82-8c88-6bb5fdef1094', …}
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/libs/api-types/src/lib/system-endpoint-calls/system-endpoint-calls-endpoints.ts (138/138 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/libs/api-types/src/index.ts (52/52 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/dto/system-endpoint-call-start-request.dto.ts (64/64 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/repositories/system-endpoint-call-event.repository.ts (70/70 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/schemas/system-endpoint-call-event.schema.ts (198/198 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/dto/system-endpoint-call-finish-request.dto.ts (91/91 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/dto/index.ts (5/5 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/dto/system-endpoint-call-batch-request.dto.ts (54/54 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/services/system-endpoint-call-tracker.service.ts (193/193 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/system-endpoint-calls.module.ts (29/29 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/system-endpoint-calls/controllers/system-endpoint-calls.controller.ts (23/23 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/main.module.ts (97/97 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/event-queue.ts (149/149 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/system-endpoint-tracking.service.ts (306/306 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/tracking-types.ts (58/58 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/system-domains.ts (187/187 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/use-system-endpoint-tracking.ts (57/57 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/tracked-fetch.ts (302/302 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/main-world-tracking.ts (314/314 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/content-script-tracking-handler.ts (328/328 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/contentScript/state/side-effects.service.ts (1019/1019 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/index.ts (11/11 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/services/system-endpoint-tracking/tracking-events.ts (55/55 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/systems/hint/patient-data/make-hint-request.ts (67/67 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/systems/elation/patient-data/elation-chart-items-progressive-service.ts (340/340 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/systems/spruce/patient-data/graphql-request.ts (79/79 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/systems/elation/patient-data/elation-patient-summary-progressive-service.ts (351/351 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/event-bridge/events/content-script-outbound-events.ts (309/309 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/chrome-extension/src/event-bridge/handlers/use-background-script-inbound-events-handler.ts (605/605 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:2782 [composer] Large diff detected for /workspace/apps/api/src/main.ts (90/90 lines). This may be due to diff timeout or whitespace issues.
workbench.desktop.main.js:55   ERR [Extension Host] [otel.error] {"stack":"OTLPExporterError: Bad Request\n\tat IncomingMessage.<anonymous> (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat IncomingMessage.emit (node:domain:489:12)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)","message":"Bad Request","code":"400","name":"OTLPExporterError","data":"{\"error\":\"Trace spans collection is not enabled for this user\"}"}
workbench.desktop.main.js:6299 [Extension Host] [otel.error] {"stack":"OTLPExporterError: Bad Request\n\tat IncomingMessage.<anonymous> (/Applications/Cursor.app/Contents/Resources/app/node_modules/@opentelemetry/otlp-exporter-base/build/src/transport/http-transport-utils.js:52:31)\n\tat IncomingMessage.emit (node:events:531:35)\n\tat IncomingMessage.emit (node:domain:489:12)\n\tat endReadableNT (node:internal/streams/readable:1698:12)\n\tat process.processTicksAndRejections (node:internal/process/task_queues:90:21)","message":"Bad Request","code":"400","name":"OTLPExporterError","data":"{\"error\":\"Trace spans collection is not enabled for this user\"}"}
4

Cont.

Create a new chat with the non-working model > result?

image
image1310×478 41.7 KB

5

Thanks for the extra info, could you try a few more steps?

Log out and log back in:

  • Cursor > Settings > General > Log out
  • Fully restart Cursor
  • Log back into your account

Temporary profile (clean environment):

  • Run in terminal: cursor --user-data-dir="CursorData/Project1”
  • A new window will open with a clean profile (no extensions/settings). Test the problematic models there
  • Closing the window will delete the temporary profile.

Let me know if it works in the temporary profile. If yes, extensions/settings are the culprit.

6

Thanks for your response!

Log out and log back in

This didn’t work.

Temporary profile

With the temp profile it’s working.

How can I debug this now?

I don’t recall installing any extension recently. Is it a “vscode” setting or a cursor setting?

8

In uninstalled the extension NX console. This seems to have solved the issue.

Name: Nx Console
Id: nrwl.angular-console
Description: The UI for Monorepos, providing visual workflows and enriching your AI Chat with deep insights
Version: 18.81.0
Publisher: nrwl
VS Marketplace Link: https://marketplace.cursorapi.com/items/?itemName=nrwl.angular-console
1 Like
9

I ran into the same issue today, also fixed by removing the nx extension.

1 Like
10

I just ran into this as well. In my case, it was one specific repo that was presenting this problem (all models I tried - including from multiple providers - returning the “Unable to reach the model provider” error except for Composer 1). I hadn’t recently installed any new extensions and that repo was working fine the last time I used it. Restarting and signing out/in did not help.

I tried testing the temporary profile approach described above with cursor --user-data-dir="CursorData/Project1”. I opened the problem repo and tested the models and they worked fine. However, when I closed it and reopened my normal Cursor application to the problematic repo, it was now working. I didn’t touch anything with any settings or extensions or anything else. So I don’t know if something about loading the repo in the temporary profile “cleaned” some problematic state in that particular repo, but…strange.

This was on MacOS with Cursor version 2.1.49 (latest available as of time of writing).

11

Actually, turns out that the temporary profile attempt left some files related to that profile in my repo, and upon deleting those, the problem returned.

I finally discovered that it seemed related to the mcp servers in this project. I have a .cursor/mcp.json file in the project with several mcp servers defined. Removing this file fixed the issue, and restoring it caused the issue to return. I went through the mcp servers individually removing/restoring them, and finally found the apparent culprit to be Vercel’s AI Elements MCP ( MCP Server ). I removed it, saved the file, tested a chat, and the models worked again. I restored the mcp server definition exactly as it was before, saved the file, tested the chat again, and the models are still working. Given the strangeness I’ve encountered I’m not entirely convinced that particular mcp server was indeed the root and only cause, although it does make some sense why this was the only repo of mine that was affected, since these are project-local mcp servers.