Clicking on custom modes selects the model set for that mode, but using hotkeys doesn’t.
Steps to Reproduce
Create two custom modes with different models. Assign hotkeys to both of them. Click on each mode and observe that the selected model changes correctly. Use the hotkey of the modes and observe that the model stays the same and only the mode changes.
Expected Behavior
The model should change to the one set for a mode when using hotkeys to select modes.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
After updating to 1.4.x, switching modes no longer switches to the model bound to that mode. This is a regression: it used to work. The mode editor still lets me assign a model to each custom mode, but the selection is ignored at runtime. Actual result: the model stays on whatever was previously selected globally, instead of the mode’s configured model.
Impact: this breaks my workflow — I rely on multiple custom modes (each bound to a different model) for fast context/model switching.
Workarounds tried: re-saving mode configs and restarting the app — no effect.
In each mode’s settings, select and save a specific model for that mode.
Start a new chat/session.
Switch between those modes.
Observe that the active model does not change to the mode’s configured model.
Expected Behavior
When I switch to a mode, the active model should automatically switch to the model configured for that mode (as it did before 1.4.x). If this change was intentional, the mode editor should not expose a model selector, or there should be a setting/toggle to preserve the prior behavior.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
I noticed that if I use the shortcut key I previously set to switch modes, the model does not switch; but if I use the mouse to click to switch modes, it switches to the model bound to that mode.
This bug relates to the custom modes beta. After creating a new custom mode with a default model and keybinding, the default model is not used when the mode is switched to using that keybinding.
Steps to Reproduce
Set a default model for the Agent mode (e.g. claude-4-sonnet)
Create a new custom mode. Assign it a keybind (e.g. ctrl+shift+.) and a default model different from the one used by Agent mode (e.g. use gpt-5)
Open a new chat in Agent mode. Note that the default model is used correctly (e.g. should be claude-4-sonnet)
Switch to the custom mode using the keybinding. Note that it is still using the default Agent model, not the different default model set for the custom mode.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.4.3
Commit: e50823e9ded15fddfd743c7122b4724130c25df0
Date: 2025-08-08T17:34:53.060Z (5 days ago)
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Cursor/1.4.3 Chrome/132.0.6834.210 Electron/34.5.1 Safari/537.36
Additional Information
This bug does not occur when selecting a custom mode using the mouse.