Hey @Yudhpt, thanks for the detailed report. Here are my recommended next steps for you:
Update to the latest version. Help → Check for Updates, then fully quit and reopen Cursor. We recently shipped a fix for one of the main causes of this.
Run network diagnostics. Cursor Settings → Network → Run Diagnostics. If you can, paste a screenshot of the results here, it tells us right away whether the connection is being blocked on the way out.
You can disabling HTTP2 and trying a Compatibility Settings in Cursor Settings → Network. It’s not a guarantee that this will fix it, but it’s possible that you might see improved behavior. (and it really depends on your network (and vpn etc) settings.
If it’s still happening after that, the most helpful thing you can send us is a Request ID from a run that got stuck: open the “…” context menu at the top-right of the chat panel and choose Copy Request ID, then paste it here. (If you have Privacy Mode enabled the ID may not be traceable on our side, but it’s still worth sharing.) That lets us trace the exact request on the backend.
Here’s how you can do that:
To disable Privacy Mode:
Open Cursor Settings with Cmd+Shift+J on macOS or Ctrl+Shift+J on Windows/Linux.
Go to General.
Turn Privacy Mode off / switch to Share Data.
To get the Request ID:
Open the relevant conversation in the Chat sidebar.