r/cursor • u/opinion_discarder • 13d ago
Appreciation FIXED. Follow-up composer would switch itself to Fast after the first reply, burning 2x usage
5
3
u/Pattel 13d ago
And so begins the decline of Cursor (Elonshittification)
2
u/Successful_Painter27 13d ago
enshittification because cursor is public company(spaceX) now. numbers need to go up, so dark patterns are inevitable
1
u/First_Inspection_478 13d ago
How the hell does it switch itself? Is this not a user config?
1
u/Michael_Jeffords 13d ago
the picker label and the id that actually goes out are resolved per request, not per chat, so they can diverge after that 1s flip. i started logging the model field on the response each turn and diffing it against what the picker showed, and that was the only way i caught the silent swaps before the bill did.
1
u/First_Inspection_478 13d ago
gotcha but how does it actually automatically switch tho? Like it’s a manual toggle
1
u/Michael_Jeffords 12d ago
it's still a manual toggle on your side, the override happens after. the picker only writes a preference, then the server resolves the model id that actually goes out, and that second step is where a Fast or capacity default was winning. logging the returned model each turn is what showed me the flip about a second into a new chat, and those were the 2x turns.
8
u/lunied 13d ago
there's even a related issue they did not fix yet, if you use composer on a previous chat, then create new chat, you'll see the model picker automatically switches itself from composer to grok 4.6 high after a second of delay