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

**URL:** <https://forum.cursor.com/t/auto-model-is-overridden-to-composer-2-5-fast-on-new-agent-chats-via-usagelimitpolicybanner/162703>\
**Category:** Bug Reports\
**Tags:** auto-mode, composer\
**Created:** [June 8, 2026, 10:17am UTC](https://forum.cursor.com/t/auto-model-is-overridden-to-composer-2-5-fast-on-new-agent-chats-via-usagelimitpolicybanner/162703 "2026-06-08T10:17:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lyudmil\_Nikodimov](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/lyudmil_nikodimov/32/110983_2.png) [@Lyudmil\_Nikodimov](https://forum.cursor.com/u/Lyudmil_Nikodimov)\
**Post date:** [June 8, 2026, 10:17am UTC](https://forum.cursor.com/t/auto-model-is-overridden-to-composer-2-5-fast-on-new-agent-chats-via-usagelimitpolicybanner/162703/1 "2026-06-08T10:17:53Z")

</div>

### 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

---

<div class="post-metadata">

**Author:** ![ErunamoJAZZ](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/erunamojazz/32/111730_2.png) [@ErunamoJAZZ](https://forum.cursor.com/u/ErunamoJAZZ)\
**Post date:** [June 15, 2026, 5:46pm UTC](https://forum.cursor.com/t/auto-model-is-overridden-to-composer-2-5-fast-on-new-agent-chats-via-usagelimitpolicybanner/162703/7 "2026-06-15T17:46:27Z")

</div>

Even using Composer 2.5 is understandable, but why in fast mode?, that mode uses more credits than the non-fast.  
This happens in Linux too, btw.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 15, 2026, 5:46pm UTC](https://forum.cursor.com/t/auto-model-is-overridden-to-composer-2-5-fast-on-new-agent-chats-via-usagelimitpolicybanner/162703/8 "2026-07-15T17:46:54Z")

</div>

Closed on July 15, 2026, 5:46pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.