Auto model: Unable to reach the model provider (ERROR_OPENAI); Muse works

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

On Windows Cursor IDE, Auto mode suddenly failed with:

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

Request IDs:

  • 51acc8f6-3588-46c2-a04a-22e43528afc4
  • 6faed0dd-0f71-4efd-b856-8d54e2cd483a
  • 8fcedba5-686a-4986-a5aa-810e479fc94c
  • cd630a43-b014-4ecb-85ff-8b6f8df28ff5

Time: around 2026-11-01 02:17–02:20 Asia/Shanghai.

Network Diagnostics in Cursor Settings were all green (DNS/SSL/API/Chat/Agent/etc.). Status page showed All Systems Operational. Pro+ account, not out of quota.

Switching from Auto to Muse made chat work again immediately. Logs showed ERROR_OPENAI / Unable to reach the model provider with server-side retries (not a transport error). This looks like an Auto routing / upstream OpenAI-provider issue.

Having to switch models breaks prompt-cache continuity and increases token cost for ongoing chats. Please look into Auto reliability.

Also emailed [email protected] with the same details.

Operating System: Windows

Steps to Reproduce

In Cursor IDE on Windows, send a chat with the Auto model selected. Around 2026-11-01 02:17–02:20 Asia/Shanghai this failed with ERROR_OPENAI / Unable to reach the model provider (server-side retries, not a transport error). Switching the same chat from Auto to Muse succeeded immediately. Network Diagnostics were all green and the status page showed All Systems Operational.

Expected Behavior

Auto mode should reach the model provider and reply, the same way Muse does, without forcing a model switch that breaks prompt-cache continuity.

Operating System

Windows 10/11

Version Information

Cursor IDE on Windows. Exact build was not captured in this report.

For AI issues: which model did you use?

Auto (failed). Muse (worked immediately as a workaround).

For AI issues: add Request ID with privacy disabled

Request ID:

  • 51acc8f6-3588-46c2-a04a-22e43528afc4
  • 6faed0dd-0f71-4efd-b856-8d54e2cd483a
  • 8fcedba5-686a-4986-a5aa-810e479fc94c
  • cd630a43-b014-4ecb-85ff-8b6f8df28ff5

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @YuanHao_Wei

This issue should be resolved now. Can you give it another try?