Selected model no longer shows whether it is thinking or non-thinking (Brain icon missing!)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The new Cursor 2.0 model selection no longer shows whether it is a thinking model or not. Previously you knew whether you were on a thinking or non-thinking model just at a glance. In 2.0, the brain icon is not shown next to the model, so I am constantly having to click and see if I’m using a thinking or non-thinking model (depending on the chat, I use one or the other as I feel most appropriate, so its never the same model, never even the same type of model…it could be Claude or something else.)

Steps to Reproduce

Select thinking model.

Expected Behavior

Selected model display should always show whether it is thinking or not by showing the brain icon for thinking models.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.34
VSCode Version: 1.99.3
Commit: 45fd70f3fe72037444ba35c9e51ce86a1977ac10
Date: 2025-10-29T06:51:29.202Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

3 Likes

i dont think that it is a bag. I think they took it out because there was not enough space because of additional icons like language browser audio
so you just nned be sure which model you use and that’s all

Right, and because I use multiple models, I’m constantly having to check and make sure that I’m usnig the right model now, because a thinking model is very different from a non-thinking one in many ways.

Seems to be plenty of space. At the very least, if there is plenty of space, they should show it, and only hide the brain if they are literally running up against the icons on the right-hand side.

3 Likes

Right. It would be great if they add add it back

This is driving me nuts! I’m keep doubting whether the model is actually reasoning.

Cursor, please put the brain icon back!

2 Likes

+1 on wanting this back. There have been several bug reports about this and many updates afterward and this is still not fixed.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The chat window no longer shows an indicator for whether the currently selected model is a thinking or non-thinking variant.

In other words, there is no visual distinction between thinking and non-thinking variants of the same model. Sonnet 4.5 and Sonnet 4.5 thinking are both displayed as just Sonnet 4.5 in the chat box when “currently selected”.

Steps to Reproduce

  1. Open a new chat.
  2. Select a thinking model from the dropdown (especially one like Sonnet 4.5, which has both a thinking and non-thinking variant).
  3. Look at the model name in the chat box. It won’t have the little brain icon, or any other “thinking model” indicator.

Expected Behavior

I expect some visual distinction to be present for thinking models. Older versions of cursor did this by putting the little brain icon next to the model name. Doing the same for 2.0.x and above would be ideal.

Screenshots / Screen Recordings

Operating System

Windows 10/11
MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43 (Universal)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0

Additional Information

I switch between thinking and non-thinking Claude models very frequently. Having no visual distinction between the two model types is making me second-guess myself multiple times in the middle of each chat, which is frustrating, especially since this wasn’t an issue on earlier cursor versions. A fix would be much appreciated!

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, I can reproduce it too – the brain icon is missing in v2.0.43, but it still shows up in v1.7 with the same extensions.

Latest version:

Version: 2.0.43
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Previous build:

Version: 1.7.54
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Looks like a regression; a staff member might want to file a bug report.

I just noticed MAX mode has the same issue as well. In 1.7.x and earlier, the “currently selected” model in the chatbox would become the purple/blue gradient to show when MAX mode was selected. However, that is also no longer the case in 2.0.x.

1 Like

Still missing in v2.0.50

1 Like

Same here.

```

Version: 2.0.54

VSCode Version: 1.99.3

Commit: 7a31bffd467aa2d9adfda69076eb924e9062cb20

Date: 2025-11-03T22:40:44.657Z (10 hrs ago)

Electron: 37.7.0

Chromium: 138.0.7204.251

Node.js: 22.20.0

V8: 13.8.258.32-electron.0

OS: Darwin arm64 23.4.0

```

This still needs to be fixed.

1 Like

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The chat does not display the selected Thinking model.

Steps to Reproduce

Select the Thinking model.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.42 (Universal)
VSCode Version: 1.105.1
Commit: 2e353c5f5b30150ff7b874dee5a87660693d9de0
Date: 2025-12-01T02:18:26.377Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

once you select an agent, it doesnt show in the input box if its the thinking or non-thinking version, which means you have to hit the pulldown to check. And if you misclick you wont know. Terrible UX. Please revert this. (There’s a reason you show it in the menu list, the same reasons apply here…!)

Steps to Reproduce

Select a thinking agent and realize you dont know if you selected the right one.

Expected Behavior

The previous versions of cursor for 12-18 months.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.47
VSCode Version: 1.105.1
Commit: 2d3ce3499c15efd55b6b8538ea255eb7ba4266b0
Date: 2025-12-04T02:31:50.567Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Cursor team closed my original topic but w/o any solution: The Thinking mode of the selected model is not displayed

@deanrie Any word on this? We are now up to Cursor 2.2…this was broken with Cursor 2.0. I can’t imagine it is a difficult feature to fix, and I’m baffled at why this is not being resolved. There still seems to be this endless march towards new features…and every time new features are released, they are buggy, often intorduce non-trivial problems, and they are left to rot.

A GOOD product, has a BALANCE of new feature work AND refinment, debugging and optimization of EXISTING features. Cursor needs to put some effort into stabilizing and debugging their existing feature base. So many features have been fundamentally broken or barely usable for a long time now, many months, while new half-baked features keep getting shunted in release after release (only to ALSO be forgotten by the next release…)

Please, support your EXISTING customer base, and fix the plethora of broken or incomplete or unstable features soon.

FWIW, this is still an issue, and I am still constantly checking to see if I’m using a thinking or non-thinking model:

This is one of many major feature-REMOVALS you guys did with the original 2.0 release. Your users have seen little to no progress on RESTORING the losst functionality. This includes other things as well, such as the loss of the ability to pop the agent panel out into its own window so it can be moved to another screen.

It really seems like you guys created a branch for 2.0 work, worked on it as a major tangent, then NEVER RE-INTEGRATED the changes being done in versions 1.5, 1.6, 1.7, 1.8, BACK INTO the branch for 2.0… So many of the innovations that were RECENTLY INTRODUCED in 1.7 and 1.8 for example, like the ability to pop out the agent panel into its own window, were just…gone. We need this functionality…it saves us time, allows us to be more efficient by effectively using our screen space (i.e. popped out agent panel), etc.

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