Cursor Agent/Ask stuck in reconnecting loop + Internal Error

Support Bug Reports
,
1

Describe the Bug

Agent is stuck in:
Planning next moves → Taking longer than expected → Reconnecting

Even “test” prompt fails.

Tried:

  • restart Cursor
  • new chat
  • Ask mode
  • reboot PC

Now getting Internal Error on server side.

Steps to Reproduce

  1. Open Cursor IDE.
  2. Create a new Agent or Ask chat.
  3. Type any prompt, including simple prompts like “test”.
  4. Cursor starts:
    “Planning next moves”
  5. Then changes to:
    “Taking longer than expected…”
  6. Then changes to:
    “Reconnecting…”
  7. Eventually shows:
    “Internal Error — An unexpected error occurred on our servers.”

Issue happens in all chats, including fresh chats.
Restarting Cursor and rebooting PC did not help.

Expected Behavior

Agent/Ask chat should respond normally to prompts instead of entering reconnecting loop or internal server error state.

Operating System

Windows 10/11

Version Information

Cursor IDE latest stable version.
Issue persists after restart and reboot.

For AI issues: which model did you use?

Claude Sonnet 4
Auto mode
Agent mode
Ask mode

For AI issues: add Request ID with privacy disabled

739ad04f-6b47-42f0-b3bc-ad54544bca09

Additional Information

Issue affects all chats and even minimal prompts like “test”.

Tried:

  • restarting Cursor
  • rebooting PC
  • creating new chats
  • switching modes
  • Ask mode
  • Agent mode

Issue still persists.

Sometimes browser requests also timeout during the issue.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report and the Request ID. The Planning next moves → Taking longer → Reconnecting → Internal Error pattern is a known one. It’s usually caused by network or HTTP/2 issues, especially if your browser requests also sometimes time out.

Let’s narrow it down. A few steps:

  1. Run Network Diagnostics: Cursor Settings > Network > Run Diagnostics. Send the results here as a screenshot.
  2. Disable HTTP/2: open App Settings via Ctrl+,, search for HTTP/2, and turn on Disable HTTP/2. Restart Cursor and test again. This often fixes similar issues on corporate networks, VPNs, or Zscaler proxies.
  3. Check your network: if you’re on a VPN, corporate proxy, or firewall, try turning it off temporarily or switch to another network like a mobile hotspot to rule out local issues.
  4. Cursor version: share your exact version via Help > About or Ctrl+Shift+P then type About.