Cursor cli --connection lost, reconnecting

Support Bug Reports
25

Does reverting to the old version above solve it? If not then there is a different issue I need to figure out

27

Is it possible to get a list of the versions and I can go back and see where it was introduced.

28

I am the user wrote the above question.

First turning off HTTP/2 seems working, but I realize it is very unstable. I have several development pipelines consiting some AI agents working together, always Cursor CLI make problems. It has not been predictable.

Now I did get rid of all Cursor agents in my pipelines, and replace them to other AI services.

Hope this issue clear asap, for paid user.

29

Thread update for everyone still seeing this issue:

Need help with diagnostics. Version 2026.04.17-479fd04 was supposed to fix some cases, but @Fullstop000 and others confirmed the bug is still there. To speed up the investigation:

  1. Request ID: if Privacy Mode is off, please post the Request ID from the debug log here. Look for request_id in agent_cli.turn.start or reqId in error logs. Without it, it’s almost impossible to find the right server logs.
  2. Your current CLI version: check with agent --version after agent update. We want to confirm which exact version still reproduces the bug.
  3. OS and repo size: even a rough estimate helps.

Current workaround: headless mode cursor-agent -p "prompt" works and goes through a different path. It’s not a replacement for interactive mode, but it works for single requests in a pipeline.

We’re tracking the issue, but I can’t give an ETA for a fix yet. I’ll post an update in the thread as soon as I have one.

30

I am still seeing the issue with version 2026.04.17-787b533. I’m on Linux (Ubuntu, kernel 6.8).

Trace id: 821d61f827c66aaec7776cc5da960674
Request id: 4d1b3ba8-c8d4-4c45-a5ef-a690d28463aa

31

I’m still facing the issue with version v2026.04.17-787b533 (macOS 26.4.1 25E253 arm64)

Is there any fix / workaround?

32

I am shocked that I am having the same problem on both WSL (i.e., Ubuntu Linux) and Windows Powershell. Both interactive (agent) and headless (agent -p "...") modes fail with Connection lost, reconnecting across:

  • All tested versions (3 builds)

  • All tested models (3 models)

  • Both HTTP/1 and HTTP/2 protocol configs

  • Both WSL2 (Ubuntu) and native Windows PowerShell

This matches the pattern described in the active bug threads. The issue appears to be a server-side streaming protocol failure affecting Ubuntu Linux and Windows (i.e., PS) clients as of late April 2026. No client-side workaround has been found that I am currently aware of.

My Request: Has anyone been able to get a response from Cursor? Is it possible to get confirmation of current server-side status for agentn.global.api5.cursor.sh and an ETA for the streaming fix?

I am a Claude Code user so I was testing out Cursor and thus far, simply unusable!

33

I’m encountering the exact same issue; Cursor is currently almost completely unusable. I hope this gets resolved soon.

34

Issue still persists. Version: 2026.05.09-0afadcc.
Environment: ubuntu docker container on MacOS
The fix works only for interactive mode. Doesn’t work for noninteractive “-p”.
{
“network”: {
“useHttp1ForAgent”: true
}
}