Hey, glad it worked. If it happens again, it looks like a known CLI streaming issue with the HTTP/2 transport. It’s being tracked in this thread Cursor cli --connection lost, reconnecting.
Workaround if it hangs again: add this to ~/.cursor/cli-config.json
{ "network": { "useHttp1ForAgent": true } }
That switches the CLI to the HTTP/1.1 fallback.
Let me know if the hang comes back. If it does, it’d help to get a dump from ~/.cursor/cli-logs/ and the CLI version at the time of the issue.
Hey, it looks like the same HTTP/2 transport issue.
Try these steps:
First: Cursor Settings > Network > Run Diagnostics. Check if anything is red.
If you’re using the IDE: open App Settings with Cmd/Ctrl+,, search for HTTP/2, turn on Disable HTTP/2, then restart Cursor.
If you’re using the CLI agent, add this to ~/.cursor/cli-config.json:
{ "network": { "useHttp1ForAgent": true } }
If it still hangs after that, share your Cursor version, OS, and whether you’re using a VPN or a corporate proxy. Zscaler and similar tools often trigger this. Logs from ~/.cursor/cli-logs/ also help if you can reproduce it in the CLI.
Thanks, your screenshots show that DNS resolution is failing for all *.cursor.sh domains, including api2.cursor.sh and authenticator.cursor.sh. So this isn’t an HTTP/2 issue, it’s a DNS issue on your side. The HTTP/2 toggle I shared above won’t help here because DNS resolution fails before it can reach the server.
Try these steps in order:
Change your DNS resolver to Cloudflare 1.1.1.1 / 1.0.0.1 or Quad9 9.9.9.9 / 149.112.112.112. Don’t use 8.8.8.8 for this case, it can cause SSL mismatch issues.
