Taking longer than expected error

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The client has been completely broken for a week now. All requests to the agent fail with the message taking longer than expected. Please note that agents work correctly through the browser and do not work at all in the client. Yesterday, there was a short period when the agent was working a little, but requests often failed with the reconnecting status.

Steps to Reproduce

Make any request

Operating System

Windows 10/11

Version Information

Version: 2.5.25 (user setup)
VSCode Version: 1.105.1
Commit: 7150844152b426ed50d2b68dd6b33b5c5beb73c0
Date: 2026-02-24T07:17:49.417Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

For AI issues: add Request ID with privacy disabled

dddb1f20-4317-4ff8-a6d1-461e51a78219

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this is a known issue affecting multiple users on v2.5.x. The fact that cloud agents work but the desktop client doesn’t points to a client network or connection issue.

Here are a few things to try:

  1. Disable HTTP/2: Press Ctrl+,, search for “HTTP/2”, enable “Disable HTTP/2”, then restart Cursor. This has helped several users.

  2. Run network diagnostics: Cursor Settings > Network > Run Diagnostics. Send a screenshot of the results here so I can see what’s failing.

  3. Reindex the project: Go to Cursor Settings > Indexing & Docs > Codebase Indexing and click Resync Index. One user with the exact same symptoms fixed it by reindexing.

  4. Try a different network: If you’re on a VPN, behind a corporate firewall, or can switch to a mobile hotspot, try that to rule out your ISP or router.

  5. Test in an empty folder: File > Open Folder > pick an empty folder, start a new chat, type “hello”. Does it still hang?

Are you using a VPN or proxy? What model are you using (Auto, Claude, Gemini, etc.)?

Related resolved threads:

The team is aware of this issue. Let me know what the diagnostics show and we’ll go from there.

Hi @deanrie ,

Disabled HTTP/2 and HTTP/1.1, but it did not solve the issue.

    "cursor.general.disableHttp1SSE": true,
    "cursor.general.disableHttp2": true,

The problem is model-agnostic.
Not using a VPN.
Switching to another network (mobile hotspot) did not solve the issue either.

Version: 2.5.26
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.4.0

I tried all of these points before creating an appeal.

  1. disabled
  2. It doesn’t help
  3. there is no way and it will not solve the problem.
  4. same problem

I tried it with and without a VPN. I tried all the models.

I managed to get a couple of answers on an empty project, after which it also fell into an endless wait

1 Like

I did some more tests based on the current situation.

My problem is fixed by disabling HTTP2 and reindexing (don’t know which of it solved the problem). However, after doing this, I can only use my OpenAI API Key, which generates response. The official Cursor auto mode still gets stuck on Taking Longer than Expected.

Version: 2.5.26 (system setup)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Hey @redfenix, your diagnostics are all green, so it doesn’t look like a network issue on your side. That means the problem is likely on the client or server side. To dig in, I need a Request ID from a failed or stuck request. You can find it in the top right of the chat panel, open the context menu, then click Copy Request ID. Without that, I can’t trace what’s happening on the backend.

Also, have you tried fully reinstalling Cursor? Since you’re on 2.5.25, try updating to 2.5.26 too. If you’re already on 2.5.26, please do a clean reinstall.

@Fernando-Fernandes, your case is different. In diagnostics, Authentication and Downloads are failing. A few things to try:

  1. Remove the disableHttp1SSE setting and keep only disableHttp2: true. With both disabled, it forces HTTP/1.0, which could be why those two endpoints fail.

  2. Check if anything on your Mac is blocking connections, like Little Snitch, firewall rules, DNS filtering, or security software.

  3. I also need a Request ID from a stuck request so I can escalate.

Once I have Request IDs from both of you, I can pass this to the engineering team.

I have tried all the methods you suggested, but the issue of “Taking longer than expected” still persists. I would like to know how to solve it. Request ID: 9ccdfde1-6092-4365-8644-7ff412b7057a

I have tried all the methods, but it didn’t work. The issue of “ taking longer than expected” still
exists.How can I avoid this problem?

1 Like

@deanrie

Request ID: c345a649-ee68-4281-96ec-d81cdc7228dc

the error has been gone for the last couple of days

the error started appearing again today 74739651-7d45-4400-b6bc-da06d38cb93e

Been getting this for the last week too. All the fixes for this error are either temporary or do not work, really doubt there is a consistent client side fix for this.

it often happen when i try to reuse an existing context window, can solve that if i switch to a new window.

Request ID: 5cf64129-6643-465d-828a-f95a6848665d

all ok