What does warming up mean?

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

the agent keep stuck in warming up , what does this mean ?

Steps to Reproduce

use agent

Operating System

Linux

Version Information

Version: 3.3.16 (Universal)
VSCode Version: 1.105.1
Commit: 7f0f522221d0ba220e4edb766bb3c47c08c14ab0
Date: 2026-05-06T20:40:56.501Z
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 25.4.0

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, Warming up… is a normal status Cursor shows while it connects to the AI backend and waits for the first token of the reply. It usually shows up for a couple of seconds and then disappears.

If it gets stuck for a long time, try this:

  • Check your internet connection. This is extra important if you’re behind a corporate proxy or VPN. Run Cursor Settings > Network > Run Diagnostics.
  • Restart Cursor.
  • Try again in a few minutes. On the free plan, the queue can be longer sometimes.

If it’s still stuck after that, send the Request ID Chat > top-right menu > Copy Request ID and the model version you’re using.

6

It keeps getting stuck again and again for me too … Just showing “Warming Up…” … Very often for some models, but also for Auto mode. This is a recent development, this never happened before, i.e. am seeing this since past week or so …

Trying to copy request ID, it simply showed “No request ID”

7

@Sharique_Abdullah hey, to figure this out we’ll need a bit of diagnostics:

  • Cursor version and OS
  • Run Cursor Settings > Network > Run Diagnostics and paste the results
  • Are you on a corporate proxy, VPN, or Zscaler? If yes, try temporarily disabling it and test again
  • Try turning on the Disable HTTP/2 option: App Settings Cmd+, > search HTTP/2 > enable it. This often helps if requests aren’t reaching the backend
  • Which models does it get stuck on most often? Only Auto, or specific ones too?

No request ID usually means the request never made it to the backend, so it’s a connection step issue, not a backend issue. The diagnostics steps above are meant to narrow that down.

8

Won’t let me respond saying, new users can only put max two links in a post …

9

@Sharique_Abdullah, this is a Discourse limit for new accounts max 2 links per post, it’s not related to Cursor.

I bumped your trust level, try replying again and it should go through. If it still gets blocked, just post the diagnostics output as plain text without active links.

10

Cursor version and OS
Version: 3.3.30 (system setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
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

Run Cursor Settings > Network > Run Diagnostics and paste the results
Cursor Network Diagnostic Results

DNS: Success
Logs:
[2026-05-15T16:27:39.077Z] Host: api2.cursor.sh
[2026-05-15T16:27:39.077Z] Servers: fd45:bbc5:bd94::1,192.168.1.1
[2026-05-15T16:27:39.077Z] Resolved to 98.85.55.115 in 8ms
[2026-05-15T16:27:39.091Z] Resolved to 98.85.55.115 in 1ms
[2026-05-15T16:27:39.108Z] Resolved to 98.85.55.115 in 1ms
[2026-05-15T16:27:39.109Z] Resolved to 98.85.55.115 in 0ms
[2026-05-15T16:27:39.109Z] Host: api2.cursor.sh
[2026-05-15T16:27:39.109Z] Servers: system
[2026-05-15T16:27:39.109Z] Resolved to 13.222.79.103, 3.231.137.26, 44.208.74.130, 23.22.11.47, 13.219.185.130, 98.85.55.115, 13.216.37.125, 34.236.111.249 in 1ms
[2026-05-15T16:27:39.109Z] Resolved to 13.222.79.103, 3.231.137.26, 44.208.74.130, 23.22.11.47, 13.219.185.130, 98.85.55.115, 13.216.37.125, 34.236.111.249 in 0ms
[2026-05-15T16:27:39.110Z] Resolved to 13.222.79.103, 3.231.137.26, 44.208.74.130, 23.22.11.47, 13.219.185.130, 98.85.55.115, 13.216.37.125, 34.236.111.249 in 0ms
[2026-05-15T16:27:39.110Z] Resolved to 13.222.79.103, 3.231.137.26, 44.208.74.130, 23.22.11.47, 13.219.185.130, 98.85.55.115, 13.216.37.125, 34.236.111.249 in 0ms
[2026-05-15T16:27:39.110Z] Result: true

HTTP/2: Success
Logs:
[2026-05-15T16:27:39.058Z] Start
[2026-05-15T16:27:39.515Z] Host: api2.cursor.sh
[2026-05-15T16:27:39.515Z] Protocol: h2
[2026-05-15T16:27:39.515Z] Result: true in 457ms

SSL: Success
Logs:
[2026-05-15T16:27:39.058Z] Start
[2026-05-15T16:27:39.677Z] URL: https://api2.cursor.sh/
[2026-05-15T16:27:39.677Z] Status: 200
[2026-05-15T16:27:39.677Z] IP: 98.85.55.115
[2026-05-15T16:27:39.677Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
[2026-05-15T16:27:39.677Z] Name: api2.cursor.sh
[2026-05-15T16:27:39.677Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
[2026-05-15T16:27:39.677Z] DNS Time: 4ms
[2026-05-15T16:27:39.677Z] Connect Time: 205ms
[2026-05-15T16:27:39.677Z] TLS Time: 201ms
[2026-05-15T16:27:39.677Z] Result: true in 619ms

API: Success
Logs:
[2026-05-15T16:27:39.059Z] Start
[2026-05-15T16:27:39.506Z] Result: true

Ping: Success
Logs:
[2026-05-15T16:27:39.059Z] Sending ping 1
[2026-05-15T16:27:39.248Z] Response: ‘ping’ in 189ms
[2026-05-15T16:27:39.248Z] Sending ping 2
[2026-05-15T16:27:39.571Z] Response: ‘ping’ in 323ms
[2026-05-15T16:27:39.571Z] Sending ping 3
[2026-05-15T16:27:39.747Z] Response: ‘ping’ in 176ms
[2026-05-15T16:27:39.747Z] Sending ping 4
[2026-05-15T16:27:39.845Z] Response: ‘ping’ in 98ms
[2026-05-15T16:27:39.845Z] Sending ping 5
[2026-05-15T16:27:40.022Z] Response: ‘ping’ in 177ms
[2026-05-15T16:27:40.022Z] Result: true

Chat: Success
Logs:
[2026-05-15T16:27:39.060Z] Starting stream
[2026-05-15T16:27:39.263Z] Response: ‘foo’ in 202ms
[2026-05-15T16:27:40.268Z] Response: ‘foo’ in 1005ms
[2026-05-15T16:27:41.272Z] Response: ‘foo’ in 1004ms
[2026-05-15T16:27:42.278Z] Response: ‘foo’ in 1006ms
[2026-05-15T16:27:43.272Z] Response: ‘foo’ in 994ms
[2026-05-15T16:27:44.260Z] Result: true

Agent: Success
Logs:
[2026-05-15T16:27:39.060Z] Starting stream
[2026-05-15T16:27:39.061Z] Pushing first message
[2026-05-15T16:27:39.238Z] Response: ‘foo’ in 177ms
[2026-05-15T16:27:39.739Z] Pushing next message
[2026-05-15T16:27:39.912Z] Response: ‘foo’ in 674ms
[2026-05-15T16:27:40.416Z] Pushing next message
[2026-05-15T16:27:40.592Z] Response: ‘foo’ in 680ms
[2026-05-15T16:27:41.095Z] Pushing next message
[2026-05-15T16:27:41.272Z] Response: ‘foo’ in 680ms
[2026-05-15T16:27:41.774Z] Pushing next message
[2026-05-15T16:27:41.953Z] Response: ‘foo’ in 681ms
[2026-05-15T16:27:41.953Z] Result: true

Marketplace: Success
Logs:
[2026-05-15T16:27:39.055Z] Host: marketplace.cursorapi.com
[2026-05-15T16:27:39.415Z] Response in 360ms
[2026-05-15T16:27:39.415Z] Response: 200
[2026-05-15T16:27:39.415Z] Response Type: cors
[2026-05-15T16:27:39.415Z] Server: null
[2026-05-15T16:27:39.415Z] Result: OK in 360ms

Authentication: Success
Logs:
[2026-05-15T16:27:39.056Z] Host: prod.authentication.cursor.sh
[2026-05-15T16:27:39.250Z] Response: 200 in 194ms

Authentication UI: Success
Logs:
[2026-05-15T16:27:39.058Z] DNS lookup: authenticator.cursor.sh
[2026-05-15T16:27:39.077Z] Resolved authenticator.cursor.sh to 104.18.35.233 in 2ms

Cursor Tab: Success
Logs:
[2026-05-15T16:27:39.058Z] DNS lookup: api3.cursor.sh
[2026-05-15T16:27:39.077Z] Resolved api3.cursor.sh to 104.18.19.125 in 2ms

Agent Endpoint: Success
Logs:
[2026-05-15T16:27:39.058Z] DNS lookup: agent.api5.cursor.sh
[2026-05-15T16:27:39.078Z] Resolved agent.api5.cursor.sh to 44.197.141.31 in 5ms

Codebase Indexing: Success
Logs:
[2026-05-15T16:27:39.058Z] DNS lookup: repo42.cursor.sh
[2026-05-15T16:27:39.093Z] Resolved repo42.cursor.sh to 34.193.164.9 in 14ms

Downloads: Success
Logs:
[2026-05-15T16:27:39.058Z] Host: downloads.cursor.com
[2026-05-15T16:27:39.280Z] Response: 403 in 222ms

CDN: Success
Logs:
[2026-05-15T16:27:39.058Z] Host: cursor-cdn.com
[2026-05-15T16:27:39.388Z] Response: 404 in 330ms

Are you on a corporate proxy, VPN, or Zscaler? If yes, try temporarily disabling it and test again

No

Try turning on the Disable HTTP/2 option: App Settings Cmd+, > search HTTP/2 > enable it. This often helps if requests aren’t reaching the backend

No

Which models does it get stuck on most often? Only Auto, or specific ones too?

Mostly, Claude Opus, Sonnet, and once or twice on Codex, and once or twice on Auto as well.