Desktop client missing Claude and GPT models

Cursor Pro account.

Dashboard and Cloud Agents correctly show Claude and GPT models.

Desktop client only shows:

  • Composer
  • Grok
  • Kimi
  • GLM

Claude and GPT disappeared today after previously working normally.

Already tried:

  • Reinstalled Cursor (3.10.17)
  • Sign out / Sign in
  • Switched HTTP/2 to HTTP/1.1 (fixed Chat HTTP 464)
  • VPN working normally

Dashboard:
Claude/GPT available.

Desktop:
No Claude/GPT models at all.

Looks like Desktop is receiving a different model catalog from the Dashboard.

Network Diagnostic:
All checks passed after switching to HTTP/1.1.

The only previous error was Chat HTTP 464, which is now resolved.

The models are still missing.

Hey, thanks for the detailed report. This isn’t a desktop catalog bug, it’s a regional restriction at the model provider level.

Anthropic, OpenAI, and Google restrict access to their models in some regions. Cursor filters those models out of the desktop client catalog based on the IP region that the request to fetch the model list comes from. That’s why only models without those restrictions remain available (Composer, Grok, Kimi, GLM). The web app and Cloud Agents run from Cursor servers, not your local IP, so they show the full list. That’s why desktop and web can differ on the same account.

Why switching to HTTP/1.1 removed chat HTTP 464 but didn’t bring models back: starting with 3.8+, AI traffic (including the model list request) is handled by a separate local process, and for HTTP/2 it doesn’t use the proxy agent due to a Node http2.connect() limitation. Those requests go direct, expose your local IP, and the catalog gets filtered by region.

What you can do:

  1. Most reliable option: enable TUN mode or a system-wide proxy in your VPN so all Cursor traffic (not just AI requests) goes through a non-CN exit IP. Then the catalog request will also go through the VPN and the full list should return.

  2. Alternative to TUN: try forcing HTTP/1.1 in settings.json by adding all four lines at once:

{
  "cursor.general.disableHttp2": true,
  "http.proxy": "http://127.0.0.1:7897",
  "http.proxySupport": "override",
  "http.proxyStrictSSL": false
}

Replace port 7897 with yours (the one your proxy listens on). It’s important to use all four lines together. http.proxy alone won’t help if HTTP/2 is enabled. After editing, restart Cursor. Quick heads up: for some users this is unstable, sometimes the list shows after the first launch, then disappears after a restart, so TUN mode is more reliable.

More on regions: Regions | Cursor Docs