Model picker: switching to models under “Other models” requires two clicks (regression)

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The new model picker splits the list into Cursor Models and a nested Other models section. I regularly switch between several third-party models (Opus / GPT / Sonnet, etc.), so switching is a high-frequency action for me.

Current behavior: if Other models is collapsed, I need two clicks every time — first expand the section, then pick the model. That adds real friction compared to the old flat list.

This matters because the models I use most often are often under Other models, not in the top Cursor Models group. Search / Cmd+/ helps a bit, but for frequent switching it’s still slower than a single click.

Suggested fixes (any of these would help)

  • Remember whether Other models is expanded across sessions (or default to expanded if the user has several models enabled there).
  • Allow pinning / favoriting models so they appear in the top-level list (regardless of Cursor vs API billing pool).
  • Keyboard shortcuts to jump directly to a specific model (or cycle only among favorited models).

Why this matters

Model switching is something power users do many times per hour. Nesting the most-used third-party models behind an extra click makes the picker feel slower for the exact workflow it should optimize.

Steps to Reproduce

  1. Open the chat model picker.
  2. Confirm several frequently used models are listed under Other models (not under Cursor Models).
  3. Collapse Other models if it is expanded.
  4. Switch from a Cursor model (e.g. Composer / Grok) to a model under Other models.

Expected Behavior

Selecting any enabled model should take a single click / key selection, same as before the nested Other models grouping. At minimum, the section should stay expanded across sessions if the user regularly uses models from that group.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

macos cursor 3.13.25

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed write-up. One key thing: this isn’t a regression or a bug, it’s the new model picker layout that’s rolling out to some users right now. So the picker may look different for different users.

A couple things that should smooth the workflow today:

  • The model you picked under Other models stays pinned at the top level of the list, so you can switch back to it with one click.
  • Search Cmd+/ filters across all models, including the ones under Other models. For frequent switching, this is usually faster than expanding the section with the mouse.

I’ll pass your suggestions along to the team, persisting the expanded state, pinning or favoriting models to the top level, and shortcuts to jump to a specific model. This is exactly the kind of signal that’s helpful for this design. There are already separate requests for pinning and shortcuts, feel free to add a vote or more details there:

I can’t share an ETA for changes yet, but the feedback is logged. Let me know if pinned model plus search doesn’t cover your use case.

follow up:

Version: 3.16.17
VS Code Extension API: 1.128.0
Commit: 6b2afae0257df2bb5e1835f15165dc2f0de056b0
Date: 2026-08-14T01:41:12.803Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

When Cursor Grok 4.6 is selected here, what’s displayed is not the model name but the effort level, which is very inconsistent.

I think this is definitely a bug.

@deanrie

Hey, thanks for the follow-up and the detailed logs. This is a different issue than the original post about model nesting. What you’re describing is that the picker trigger shows the effort level Extra High Fast instead of the model name when Cursor Grok 4.6 is selected.

This is a separate issue we’re already tracking, so it’s not something misconfigured on your side. I can’t share a timeline yet, but I’ll reply here when there’s an update.

One small ask: since this isn’t about the original thread topic nesting under Other models, could you move this to a separate thread? It’s easier for us to track this issue without mixing it with layout feedback. If you create one, send the link and I’ll tie it to the rest.