I’ve noticed a change in how custom modes handle model selection in Cursor version 0.50. In previous versions, when I set a specific model for a custom mode, that model would remain tied to the mode regardless of mode switches. However, in 0.50, when I switch between modes, the model no longer follows the custom mode’s settings and stays stuck on a single model (seemingly the last one used) unless I manually change it.
**For example: **
I set Custom Mode A to use Sonnet3.7 and Custom Mode B to use GeminiPro2.5.
In earlier versions, switching to Mode A would automatically use Sonnet3.7, and Mode B would use GeminiPro2.5.
Now, if I’m in Mode A using Sonnet3.7 and switch to Mode B, it still uses Sonnet3.7 unless I manually select GeminiPro2.5.
Has anyone else encountered this issue? It feels like a regression from the previous behavior, as it disrupts the workflow when switching modes. I’m running Cursor 0.50 on Windows 11. Any workarounds or insights would be appreciated
