Hi @tsufleta
Your Network Diagnostics screenshots clearly identify the issue. Your corporate network is running Netskope as an SSL-inspecting proxy (ca.publicisgroupe.de.goskope.com), which is intercepting and re-signing all encrypted traffic to Cursor’s servers.
This causes two problems:
-
HTTP/2 fails entirely because the proxy doesn’t support HTTP/2 ALPN negotiation
-
In HTTP/1.0 mode, streaming is buffered by the proxy, which is why agents appear stuck at “Planning next moves” / “Taking longer than expected” before eventually returning a response all at once
Indexing failures are a downstream effect of the same connectivity issue.
The fix is on your IT/network side. The most effective solution is to have your IT team exclude Cursor’s domains from Netskope SSL inspection. These are the domains to allowlist/bypass:
*.cursor.sh
*.cursor-cdn.com
*.cursorapi.com
authenticate.cursor.sh
authenticator.cursor.sh
Our Enterprise Network Configuration docs cover this in detail, including curl commands your IT team can use to verify the fix.
If SSL inspection can’t be disabled for those domains, a secondary option is to have IT install the Netskope CA certificate into your macOS system Keychain (as a trusted root), then in Cursor press Cmd+Shift+P and open “Preferences: Open User Settings (JSON)” and add:
"http.systemCertificates": true,
"http.experimental.systemCertificatesV2": true
Keep HTTP/1.0 selected in Cursor Settings > Network for now, as HTTP/2 won’t work through Netskope.
Regarding the GitHub login popups: this is a separate issue. Try pressing Cmd+Shift+P and running “GitHub: Sign Out” to clear cached auth state. If that doesn’t stop the popups, you can also disable the built-in GitHub Authentication extension: go to the Extensions view, type @builtin github in the search bar, and disable GitHub Authentication.
A similar thread with the same class of proxy issue was resolved here: Unable to verify first certificate