Model reverts to composer-2-fast on each new chat

[Peter_WBD (Peter)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using the Agent sidebar panel in the Cursor IDE, the selected Model reverts to Composer 2 Fast whenever opening a new Chat.

I am using Composer 2 (non-fast), however I keep finding that it reverts to Composer 2 Fast whenever opening a new conversation tab or after a few prompts.

Steps to Reproduce

Open a new conversation, set the Agent to Composer 2, give it a prompt, then open a new tab - it will have reverted to Composer 2 Fast.

Expected Behavior

The Agent should stay on Composer 2 - the latest Agent that I have manually selected.

Screenshots / Screen Recordings

Composer 2 Model is selected…

Upon opening a new tab, composer-2-fast is selected…

Operating System

Windows 10/11

Version Information

Version: 2.6.20 (user setup)
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
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
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report.

This is a bug. When you open a new chat, the model selection for Composer 2 is being silently switched to Composer 2 Fast. The team is aware of similar model persistence issues, and I’ve flagged this specific case. There’s no timeline yet, but your report helps us prioritize.

As a workaround for now, try selecting the model again after opening a new tab. Unfortunately, there’s no permanent client-side fix until this gets patched.

Let me know if anything else comes up.

[davidshq (Dave Mackey)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m using the new Cursor 2 model, but I want to use Cursor 2 and not Cursor 2 Fast because the former is 1/3rd the cost. Yet it seems that Cursor is regularly flipping me over to Cursor 2 Fast. It’s very frustrating. Is anyone else experiencing this?

Steps to Reproduce

Set in chat to use Composer 2.

Expected Behavior

Stays with Cursor 2 and does not change to Cursor 2 Fast without me selecting it.

Operating System

Linux

Version Information

Version: 2.6.20
VSCode Version: 1.105.1
Commit: b29eb4ee5f9f6d1cb2afbc09070198d3ea6ad760
Date: 2026-03-17T01:50:02.404Z
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
OS: Linux x64 6.8.0-101-generic

For AI issues: which model did you use?

Cursor 2

Does this stop you from using Cursor

No - Cursor works, but with this issue

[SavanM (Savan Masipeddi)]

Same here.

[davidshq (Dave Mackey)]

Maybe we can not be charged at the Fast rate until this is fixed?

[Martin_Schoenholzer (Martin Schönholzer)]

Don’t be paranoid. The composer/auto pool is very generous.

[troehrkasse (Tyson Roehrkasse)]

Same thing here. Still getting auto-selected even though manually disabled

[Chris_Valentine]

this happening to me also. quite annoying. I even disabled the model, and it still tries to use it… sigh

[gemyagouatc (Eugene Myasyshchev)]

same here, it’s very annoying, before it used my last model, now it throws fast on me every time. Cursor team, please fix this

[Colin]

Hi all!

No conspiracy here. It’s a bug, and we’re going to fix it.