Why am I seeing Composer 2.5 fast (when Fast is not selected)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’ve Composer 2.5 selected with ‘Fast’ mode off. But seeing Composer 2.5 Fast being used for changes?

Steps to Reproduce

Select Composer 2.5 turn off the Fast option. Make a change.

Expected Behavior

Should be using Composer 2.5 not Composer 2.5 Fast.

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 3.11.19
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z
Layout: Agent Window
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 6.17.0-40-generic

For AI issues: which model did you use?

Composer 2.5 (not Fast variant)

Additional Information

Sorry this is my first post and it is a bug. Love Cursor and the work you do.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Two separate things can surface “Composer 2.5 Fast” when you’ve toggled Fast off:

  1. On the main agent, the Fast label can show (or flip back on after a prompt) even with the toggle off - a known display/state bug in the Composer 2.5 picker. To be sure a run isn’t Fast, toggle it off right before submitting and confirm the picker reads just “Composer 2.5”.
  2. The built-in Explore subagent currently uses the Composer 2.5 Fast variant regardless of that toggle - a separate known issue. If you’d rather avoid it, you can disable the Explore subagent or point it at a different model in Cursor Settings (Subagents).

Both are things we’ve seen reported and are tracking - no fix has shipped yet, but I’ve logged your report and will update here when there’s progress.

Thank you I appreciate the advice and the response.

Edit:
The above resolved my issue. Now using Composer 2.5 as defined.