Let’s go!
Hey all - quick update. The fix for chat/agent/API requests bypassing your HTTP proxy on proxy-only networks is now in and rolling out in an upcoming 3.11 patch. Once you’re on a newer build, please give it another go and let us know if any traffic is still slipping past the proxy.
A few notes on the workarounds in this thread while you wait:
Forcing HTTP/1.1 with your proxy is the safest stopgap. Set these, then fully quit and relaunch (full Quit, not Reload Window):
{
"cursor.general.disableHttp2": true,
"http.proxy": "http://127.0.0.1:7890",
"http.proxySupport": "override",
"http.proxyStrictSSL": false
}
Use your own proxy address and port. Some of you saw this behave inconsistently on 3.9.x/3.10.x - that’s the same root cause, and the upcoming patch is the real fix.
Please don’t delete or rename %APPDATA%\Cursor / %USERPROFILE%\.cursor (or the macOS equivalents). Thanks for sharing it @contorju but it only helps for a few hours and it wipes your chat history, settings, and extensions.
The scripts that edit Cursor’s local database or reroute specific domains at the network layer can bring things back temporarily, but they change internals that aren’t meant to be modified and tend to break on the next update. Appreciate @Anveena and others putting in the effort - I’d treat those as last-resort stopgaps rather than something to keep in place.
I’ll update this thread once the patch is out - reply here if it still persists after you update.