HelpPlease check whether my desktop client is receiving an incorrect model catalog or feature flag configuration

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Desktop app only shows:

  • Composer 2.5
  • Grok Build 0.1
  • Grok 4.3
  • Kimi K2.5

My account is Cursor Pro.

On the web dashboard / Cloud Agent I can access:

  • GPT-5.5 High
  • GPT-5.4 High
  • Opus 4.8 High
  • Sonnet 4.6 High
  • Codex 5.3 High

But these models do not appear in the desktop app.

What I’ve already tried:

  • Sign out / sign in
  • Delete local cache (globalStorage)
  • Reinstall Cursor
  • Update to latest version (3.7.27)
  • Refresh model catalog

The issue only affects the desktop app.

Please check whether my desktop client is receiving an incorrect model catalog or feature flag configuration.

Steps to Reproduce

i suddenly met this issue,i dont know how to reproduce it.

Operating System

Windows 10/11

Version Information

Version: 3.7.27 (user setup)
VS Code Extension API: 1.105.1
Commit: e48ee6102a199492b0c9964699bf011886708ba0
Date: 2026-06-10T01:46:16.942Z
Layout: glass
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
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, this isn’t a bug with the client config, it’s a regional restriction.

Anthropic Opus and Sonnet, OpenAI GPT-5 and Codex, and Google restrict access to their models from some regions at the provider level. Cursor filters these models out of the server catalog based on the request IP, so they don’t show up in the desktop app. Models that aren’t affected, like Composer, Grok, and Kimi, stay available, so those are the ones you see.

Why the web dashboard and Cloud Agent show the full list: those requests come from Cursor servers, not your local IP, so the regional filter doesn’t apply there. That’s why there’s a split between desktop and web. Client steps like signing out and back in, clearing cache, reinstalling, or refreshing the catalog won’t help, since the filtering is server-side by IP.

Cursor can’t bypass this. Full model access in desktop is only possible when connecting from a supported region. More details: Regions and model availability | Cursor Docs

This was discussed here too if you want more details: Linux + Glass: Settings and model picker only show four models (Pro+)