Stuck on planning next moves and throughing server errors

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m on ultra plan using auto mode and also specific model modes
getting so many issues today with timeouts, server issues, stuck on planning mode etc

Steps to Reproduce

use cursor for a few hours and then nothing works

Expected Behavior

the auto and manual models work consistently. lol
basic requirement for your product really yet every week I’m having days/hours of downtime between days of great output with no issues

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.32 (system setup)
VSCode Version: 1.105.1
Commit: ef979b1b43d85eee2a274c25fd62d5502006e420
Date: 2025-11-25T05:00:12.749Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

auto sonnet 4.5

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Hey, thanks for the report. I see you’re experiencing timeouts and hangs in agent mode. According to recent similar reports, this is usually caused by either extensions or network environment issues.

Please try the following steps in order:

  1. Test without extensions:

    • Run cursor --disable-extensions in CMD
    • Open agent chat (don’t open a repo)
    • Try a simple request to see if it responds
    • If it works, disable extensions one by one to find the culprit

  2. Network diagnostics:

    • Go to Cursor Settings > Network > Run Diagnostics
    • Share a screenshot of the full results

  3. HTTP/2 setting:

    • Open Settings Ctrl+, > search “HTTP/2”
    • Enable “Disable HTTP/2”
    • Restart Cursor

  4. Check your environment:

    • Are you using a VPN? Try disabling it
    • Firewall/antivirus software? Try temporarily disabling
    • Corporate network/proxy?

Also, could you share 2-3 Request IDs from failed attempts? (Chat context menu > Copy Request ID right after the error)

Let me know what you find - this will help determine if we need to escalate to engineering.

3

It’s not caused by network issues or extensions.

It’s caused by some hidden rate limit/usage limit either in cursor or the AI models.

It consistently happens after several hours of working in cursor.

Then it consistently fixes itself again and all is well.

It’s very frustrating because everything is working great, then I get hit with several hours of nothing working, and then it randomly starts all working again.

I’ve done network tests before, during and after. The network is exactly the same and has even been stronger results during the broken chats. I’ve tested this several times since it happens so frequently.