Cursor seems to be intentionally forcing use of their Composer model

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor is intentionally forcing users to use their composer model.

It is impossible to remove it permanently from the models list in the settings. IT always switches to composer when switching between ask and Agent which causes confusion and hollucinations. The model is terrible and makes consistent mistakes, its at the level of flash 2 at the most.

Steps to Reproduce

Go to settings and disable composer. Cursor intentionally adds it back through their programming minutes later. This does not occur with other models so it definitely seems intentional. Cursor has had months to fix this issue making it seem intentional rather than a bug. They also switch to composer whenever they find a chance mid conversation or when switching between ask and agent mode. They offer a workaround of setting a default model per conversation type but it also switches to composer and doesn’t work.

Expected Behavior

Users should be able to disable composer in the cursor settings. Conversations should not switch models without the users changing the model.

Operating System

Windows 10/11

Version Information

IDE; 2.3.34

For AI issues: which model did you use?

any model it always switches to composer at some point.

Additional Information

Cursor is aware of the problem since its launch. It seems intentional and this is false advertising and deceptive trade practices.

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report.

A few questions to understand what exactly is happening:

  1. When exactly does it switch to Composer?

  2. Cursor version: you’re on 2.3.34. The issue where it switched to Composer on send was fixed. Please try updating to the latest version.

  3. About “impossible to remove from settings list”: what exactly do you mean? Which settings are you trying to remove Composer from? A screenshot would help.

  4. Subscription status: do you have an active Pro subscription? Some models are only available on paid plans.

If it’s the same issue as in thread #147772, it was on our radar as a priority. If updating doesn’t fix it, please share the Request ID and the exact steps that trigger the switch.