Freezed: Taking longer than expected

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After any request in the chat (even a very simple one), the message “Taking longer than expected…” appears and just hangs forever (10+ minutes, never finishes).
Restarting Cursor, restarting the PC, clearing cache, switching models, disable HTT2 - nothing helps.
The problem appears right from the very first message in a new chat.

Steps to Reproduce

Open Cursor.
Start a new chat or agent.
Write any prompt (for example, “hello” or “hi”).
Press send → it gets stuck forever on “Taking longer than expected…”

Expected Behavior

The model’s response comes normally.

Screenshots / Screen Recordings

Operating System

Linux

Version Information

Version: 2.5.20
VSCode Version: 1.105.1
Commit: 511523af765daeb1fa69500ab0df5b6524424610
Date: 2026-02-19T20:41:31.942Z
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: Linux x64 6.17.0-14-generic

For AI issues: which model did you use?

Composer 1.5

For AI issues: add Request ID with privacy disabled

RequestID: 39e22aaf-3f39-4abe-be93-5a6df21d3c49

Does this stop you from using Cursor

Yes - Cursor is unusable

1 Like

Hey, thanks for the report. This is a known issue, a few users are seeing the same thing on v2.5.20.

I see you’ve already tried disabling HTTP/2, switching models, and restarting. A couple more things to check:

  1. Network diagnostics: Cursor Settings > Network > Run Diagnostics. Please post the results here. I want to confirm your network connection looks OK.
  2. Try switching networks. If you can, connect via a mobile hotspot to rule out an ISP, VPN, or firewall issue.

This is on our radar. Let me know what the diagnostics show.

i forgot to say that im already ran the network diagnostics and its is OK, i have two network providers in my house, after change the the provider cursor works, probably the problem can be a router configuration or a problem between service provider and cursor servers

1 Like

Glad you got it sorted out. The issue is on the first provider’s side, most likely their firewall or router is blocking certain requests to Cursor servers.

This is useful info for other users with similar symptoms. I’ve marked the topic as solved.