Auto model is overridden to Composer 2.5 Fast on new agent chats via UsageLimitPolicyBanner

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When Auto is selected in the agent model picker, starting a new agent chat (or opening a workspace) causes the selector to switch to Composer 2.5 Fast without my action.

Client logs show this is triggered by UsageLimitPolicyBanner:

UsageLimitPolicyBanner: auto-switched composer to allowed model
fromModel: default
toModel: composer-2.5
(default = Auto; composer-2.5 = Composer 2.5 Fast in the UI.)

Expected: If Auto is already selected, new chats should keep Auto. Auto and Composer 2.5 both use the Auto + Composer usage pool per Cursor docs, so switching from Auto → Composer 2.5 is unnecessary and confusing.

Actual: The model picker changes to Composer 2.5 Fast. Re-selecting Auto can flip back to Composer 2.5 within seconds.

Steps to Reproduce

  1. Open Cursor (unified agent panel).
  2. Set the agent model to Auto.
  3. Start a new agent chat (or open a project).
  4. Observe the model picker — it shows Composer 2.5 Fast instead of Auto.

Expected Behavior

If Auto is already selected, new chats should keep Auto. Auto and Composer 2.5 both use the Auto + Composer usage pool per Cursor docs, so switching from Auto → Composer 2.5 is unnecessary and confusing.

Operating System

MacOS

Version Information

Version: 3.7.19 (Universal)
VS Code Extension API: 1.105.1
Commit: 80c653c2c3528e65016a0d304b54486084b470b0
Date: 2026-06-07T01:42:56.126Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue