Cursor agent stalls / gets stuck

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor agent stalls / gets stuck when performing external operations.

This has worked flawlessly until last week, but now, whenever i try to do something, the agent gets stuck at various operations.

It often gets stuck on “Planning next move”, but also when trying to search or fetch from online resources, and especially when trying to execute commands, the execution is either very slow (5-10sec for simple commands, i.e. ‘ls’ ) or they get cancelled or the agent ends up stuck with “Reconnecting…”.

If i try to rerun the prompt, it quickly gets stuck again.

I have updated Cursor IDE and rebooted my pc.
Changing model or mode doesnt fix the issue.

Yesterday i had it working for some hours, but now its not working again.
Also tried switching to a different network.

I am currently working on a WSL device, but i have the same issue regardless if its executing normal terminal operations or on a local WSL device, although local seem to be a bit more stable.

Steps to Reproduce

Perform any command that requires ‘external operations’, i.e. online searching, or terminal commands.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 2.4.36 (user setup)
VSCode Version: 1.105.1
Commit: f9919bf991f247689f9ead605b5c5a3239a2a790
Date: 2026-02-12T21:00:33.976Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report “Planning next moves”. This is a known class of issues and it’s usually related to networking or connectivity. WSL adds an extra layer of complexity.

Let’s try the following:

  1. Disable HTTP/2: Open Settings with CTRL + ,, search for “HTTP/2”, and enable “Disable HTTP/2”. Then restart Cursor.

  2. Network diagnostics: Go to Cursor Settings > Network > Run Diagnostics and send a screenshot of the results.

  3. Console errors: When it gets stuck, open Help > Toggle Developer Tools > Console and take a screenshot of any red errors. This helps confirm if it’s a transport or streaming issue.

  4. Test without WSL: Open a simple local folder (not in WSL) and try a basic prompt. If it works locally but not via WSL, the issue is likely in WSL’s network layer.

  5. Test via mobile hotspot: Connect your PC to your phone’s mobile internet (not your Wi-Fi router) and try again. If it works, the issue is likely your network, ISP, or firewall.

Also, if you’re on a corporate network, corporate proxies and firewalls are a common reason streams hang. Check with IT if traffic inspection or SSL interception is enabled.

A similar case was fixed by renaming the project folder to force a new cached workspace: Connection Error / Stalled Agent requests for hours. Worth trying if the steps above don’t help.

Send back the diagnostics results and we’ll dig in further.

The HTTP/2 setting was already disabled.
I ran the network diagnostics tests, which failed at API and Agent.
Uploaded log file for local prompt attempt (no WSL).
Tried 2 different hotspots, didnt change anything.

Most likely it’s a company network security issue.
We’re using Zscaler, which breaks a lot of stuff.
IT department / ZScaler probably made security updates recently, which broke cursor usability.

Same issues here. Any versions after 2.2 will have the issue.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.