Model Thinking Effort Selection is Missing

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The model thinking effort is missing from model selection.

Steps to Reproduce

In the chat window, click on the model dropdown, and the models with different effort levels are missing. If you click Add Models, in Settings it shows all the list of available models. However, models with different levels of effort are not listed in settings either (see screenshot). Also, if you hover over the model selection dropdown, it shows a keyboard shortcut for cycling model and a separate keyboard shortcut for cycling thinking effort (see screenshot). But the Cycle Effort shortcut doesn’t do anything.

Expected Behavior

Before installing the most recent update, these were the options that were available for Opus 4.7: Low, Medium High, Extra High. (see attached screenshot, from before the most recent update). I should, for instance, be able to select Opus 4.7 Medium.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.1.17 (system setup)
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
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
OS: Windows_NT x64 10.0.26200

Additional Information

I have found that for most of my tasks, Opus 4.7 with Medium thinking effort pulls in a good amount of context, doesn’t spend too much time in the thinking step, and provides good results. This bug is forcing us to use Opus 4.7 with High thinking effort. This not only wastes tokens and processing time, but I have found that in High thinking effort the model overthinks and ends up producing poorer results.

Does this stop you from using Cursor

No - Cursor works, but with this issue

The forum post bug report template wouldn’t let me include more than one screenshot template, so here are the others:

Evidence that this was available before installing the most recent update:

Even in the current update, there is still a tooltip indicating a keyboard shortcut for toggling Cycle Effort, but it doesn’t do anything:

Screenshot 2026-04-20 092338

Hi @Leland_Hepworth!

This is the new model picker, and you can switch between thinking levels by clicking Edit

Yes, that does let me change the model effort.

The Keyboard Shortcut still doesn’t work, but now I at least know how to do it from the dropdown. Thanks!

Thanks for the clarifications. Is there a keyboard shortcut on Mac for toggling fast off and on? Before I updated Cursor, my flow was generally cmd+/ in order to select a model and I’d just type something like ‘high fast’ to find the Codex model I wanted, or ‘max’ to find the Opus model I wanted. Now with the update, I can cmd+/ to select the family, then cycle through the reasoning with cmd+shift+/ but … the only way to toggle fast is by clicking through the menu, it seems.

If there is a way I’d love to know, otherwise it would be a nice to have :slight_smile:

Hey @nemo_nemini!

No way to toggle Fast Mode with the keyboard right now. It might make a good Feature Request!

It’s a bug, because the hover tooltip indicates that there’s a keyboard shortcut to “Cycle Effort,” but it doesn’t work:

Screenshot 2026-04-20 092338

Cycling effort shortcut works for me on Mac, but I notice you’re using Windows. Not sure if there is an OS-level difference with this feature.

Also, do you have any global key board shortcut (or perhaps for a different app) which might be overriding the Cursor one? I have previously had issues with that and it just requires either changing the Cursor keyboard shortcut OR the other app one which are in conflict.

Nice catch @nemo_nemini! We do have a bug open with regards to cycling effort on Windows (it currently conflicts with another action that opens the Agents view).

This is also a problem on Macs - for me, ⇧⌘/ opens the Help menu and puts the cursor into a search box.

The new interface for thinking levels is very awkward for those of us who frequently switch between a couple of levels for different tasks. The previous view allowed for e.g. just high and xhigh to be quickly chosen. Even if the keyboard shortcut worked, it’s still much worse UX.

Version: 3.1.17 (Universal)
VSCode Version: 1.105.1
Commit: fce1e9ab7844f9ea35793da01e634aa7e50bce90
Date: 2026-04-19T19:33:58.189Z
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
OS: Darwin arm64 24.6.0

@jonbride Can you let me know if it’s working better for you on 3.3.12? Haven’t been able to reproduce internally.