When using the Agent sidebar panel in the Cursor IDE, the selected Model reverts to Composer 2 Fast whenever opening a new Chat.
I am using Composer 2 (non-fast), however I keep finding that it reverts to Composer 2 Fast whenever opening a new conversation tab or after a few prompts.
Steps to Reproduce
Open a new conversation, set the Agent to Composer 2, give it a prompt, then open a new tab - it will have reverted to Composer 2 Fast.
Expected Behavior
The Agent should stay on Composer 2 - the latest Agent that I have manually selected.
This is a bug. When you open a new chat, the model selection for Composer 2 is being silently switched to Composer 2 Fast. The team is aware of similar model persistence issues, and I’ve flagged this specific case. There’s no timeline yet, but your report helps us prioritize.
As a workaround for now, try selecting the model again after opening a new tab. Unfortunately, there’s no permanent client-side fix until this gets patched.
I’m using the new Cursor 2 model, but I want to use Cursor 2 and not Cursor 2 Fast because the former is 1/3rd the cost. Yet it seems that Cursor is regularly flipping me over to Cursor 2 Fast. It’s very frustrating. Is anyone else experiencing this?
Steps to Reproduce
Set in chat to use Composer 2.
Expected Behavior
Stays with Cursor 2 and does not change to Cursor 2 Fast without me selecting it.
Something is telling me this is very deliberate. I disabled composer 2 fast within the settings and yet it still shows up as default and requests still get routed to the more expensive model no matter what.
The composer/auto pool is very generous.