Is it just me or does Cursor switch from Cursor 2 to Cursor 2 Fast sporadically?

Support Bug Reports
,
1

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

4

2 posts were merged into an existing topic: Model reverts to composer-2-fast on each new chat

5

Hey, this is a known bug. The Composer 2 model selection doesn’t persist and resets to Composer 2 Fast when you open a new chat. Others are seeing the same issue too: Model reverts to composer-2-fast on each new chat

The team is aware and tracking it.

For now, the only workaround is to manually re-select Composer 2 in each new chat. Not ideal, but your existing chats should keep the correct model.

1 Like