Default model resets to Composer 2.5 Fast despite selecting Composer 2.5 with Fast disabled

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

My default agent model keeps reverting to Composer 2.5 Fast even when I explicitly choose Composer 2.5 with Fast turned off. This happens on startup, when opening a workspace, and when starting new agent chats.

Client logs show UsageLimitPolicyBanner auto-switching from default (Auto) to composer-2.5, and the UI then shows Composer 2.5 Fast. The fast=false preference does not appear to persist.

Steps to Reproduce

  1. Open Cursor (unified agent layout).
  2. In the agent model picker, select Composer 2.5.
  3. Open model parameters and turn Fast off.
  4. Close and reopen Cursor, or start a new agent chat, or open a project folder.
  5. Check the model picker.

Alternate repro (also observed):

  1. Set the agent model to Auto (default).
  2. Open a workspace or start a new agent chat.
  3. Model picker switches to Composer 2.5 Fast without user action.

Expected Behavior

  • Composer 2.5 with Fast disabled should stay selected across sessions and new chats.
  • If Auto is selected, it should remain Auto unless I change it.
  • Auto-switching to an allowed model should respect my fast=false preference, or at least not default to the Fast variant.

Operating System

Linux

Version Information

Version: 3.9.16
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Linux x64 7.0.10-1-MANJARO

Does this stop you from using Cursor

No - Cursor works, but with this issue

8

Hi @JoaoBoing Thanks for reporting this. This is a known behavior, some of it is intentional and some of it is not. We do truly try to push users toward Composer 2.5 fast as opposed to regular as a default because we think it provides the best experience.

However, there is also a bug here as well, which you confirmed with the log messages you have shared. When your team hits its usage limit, Cursor auto-switches new chats to Composer 2.5 and drops your Fast-off preference, and we’ve flagged it for the team to fix. As a workaround, since you’re the team owner, raising your team’s usage / on-demand limit stops the auto-switch from triggering; re-selecting Composer 2.5 with Fast off also holds within a chat in the meantime.

We’ll keep you updated on the status of the bug and let you know any updates

9

>We do truly try to push users toward Composer 2.5 fast as opposed to regular as a default because we think it provides the best experience.

Hey @kevinn, please respect our choice to turn off Fast. It’s a significantly higher token usage and being able to use Cursor for the whole month is a good tradeoff for a slower model.