Describe the Bug
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.
Related discussion: Bind a model to each mode and remember it.
Steps to Reproduce
- Create two or more custom modes.
- 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)
Version: 1.4.3 (Universal)
VSCode Version: 1.99.3
Commit: e50823e9ded15fddfd743c7122b4724130c25df0
Date: 2025-08-08T17:34:53.060Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
Does this stop you from using Cursor
No - Cursor works, but with this issue