Cursor Keeps Reconnecting or Connection Failed

How to fix it

Try these in order — the most common fix is first.

1. 1. Disable HTTP/2

   Copy steps
   1. Settings > search HTTP/2 > enable Disable HTTP/2
   2. Quit and reopen Cursor
   Did this fix it? Yes No

2. 2. Allow Cursor domains

   Copy steps
   1. Allowlist or bypass SSL inspection for *.cursor.sh, *.cursor.com, *.cursorapi.com, *.cursor-cdn.com
   2. Make sure the proxy allows streaming responses without buffering
   Did this fix it? Yes No

3. 3. Restart Cursor after the network recovers

   1. Fully quit and reopen; staff acknowledged a stuck-status bug
   Did this fix it? Yes No

4. 4. CLI users

   1. Set useHttp1ForAgent in .cursor/cli_config.json as reported by users
   Did this fix it? Yes No

Symptoms

Agent shows Reconnecting after every action, connection stalled, ConnectError unavailable, or stuck Thinking.

Why it happens

• Corporate proxy or VPN breaking HTTP/2 streaming
• SSL inspection or response buffering
• Known client bug where status stays stuck after the network returns
• Hotspot or unstable network

This guide also covers

• cursor reconnecting
• cursor connection failed
• cursor stuck on planning next moves
• cursor connectError unavailable

Other Cursor errors

• Cursor Usage Limit Reached
• Cursor Rate Limit Exceeded
• Cursor Agent Not Working
• Cursor High Load Error (ERROR_RESOURCE_EXHAUSTED)
• Cursor Extensions Not Working or Not Found
• Cursor Slow, High CPU or Memory Usage
• Cursor MCP Not Working: Server Connected but No Tools
• Can't Use Cursor Auto After Included Usage Is Gone