Critical Bug: Cannot Switch Models After Using O3 – Error When Switching

Support Bug Reports
1

Describe the Bug

After using the O3 model in a conversation, switching to any other model (including OpenAI models) becomes impossible. This seems to occur only after O3 uses tools/plugins during the session.

This issue is highly disruptive because O3 is often excellent at identifying bugs, but I prefer using another model for code fixes or explanations. Currently, once I use O3, I’m locked into it for that conversation

Steps to Reproduce

Open a new conversation in Cursor.

Ask a question using the O3 model.

Let O3 use its tools (e.g. search, code runner).

Attempt to switch to any other model (GPT-4, Claude, etc.).

The following error appears, and the switch fails.

Error Message:

:warning: We’re having trouble connecting to the model provider. This might be temporary – please try again in a moment.
Request ID: bca47a22-b53e-4713-b4fd-d3f87ef802cc

This is misleading: there is no real connectivity problem, as all models load fine in other conversations.

Expected Behavior

After using O3, I should still be able to switch models within the same conversation, especially when I don’t want tool access anymore.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Cursor Version: 1.2.4 (user setup)

VSCode Version: 1.99.3

Commit: a8e95743c5268be73767c46944a71f4465d05c90

Electron: 34.5.1

Chromium: 132.0.6834.210

Node.js: 20.19.0

V8: 13.2.152.41-electron.0

OS: Windows_NT x64 10.0.19045

Additional Information

The issue consistently occurs after O3 uses tools.

No model-switching issue in other conversations or fresh threads.

Would appreciate confirmation if others are seeing this too, and whether there’s a current workaround.

Thanks in advance!

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
O3 - pro user - not connecting to model provider
O3 - pro user - not connecting to model provider
2

Hey, thanks for the report, we’ll investigate it.

2 Likes
3

Same here. The issue occurs with o4-mini as well. Here’s some additional context and a stack trace (essentially the same as your info):

4

@yakovw Are you still able to reproduce this? It seems fixed for me as of today.

1 Like
5

You are right, it has been fixed
Thank you very much
You have accepted my idea, how to take Cursor to the next level, which will double the usability, save a lot of money for both users and you, and also make the agent much smarter
I sent this to Sam a few days ago, I don’t know if anyone actually read it.

‫בתאריך יום ב׳, 21 ביולי 2025 ב-19:34 מאת ‪scupit via Cursor - Community Forum‬‏ <‪[email protected]‬‏>:‬

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.