I experience issues with Cursor Pro v0.47.8 when using Agent mode and MCP, as the servers fail to connect. While chat mode and normal code execution function correctly, the problem persists unless Zscaler is exited—a workaround that is not feasible since both Zscaler and Cursor need to run simultaneously.
This issue was initially reported to hi@cursor while using version 0.46. After some time, support suggested upgrading to v0.47.8, claiming that adjustments had been made to resolve it. However, the problem remains unresolved. Needless to say I diasbled HTTP2…
Interestingly, other coding agents such as Blackbox and ZenCode do not exhibit the same issue. Cursor remains the preferred choice due to its all-in-one functionality, and a one-year subscription has already been purchased.
Facing the same issue, and to confirm - are you saying that disabling http2 can at least enable chat/edit mode?
Without disabling that, I got NGHTTP2_INTERNAL_ERROR error. And with disabling, chat/edit would work but not stream (which I prefer), so just a partial workaround. I guess agent model fails because it heavily relies on the streaming capability or something like that.
As a newbie to Cursor (started using it at v0.46), I must say I’m pleasantly surprised that at least the Edit Mode is working smoothly. The Chat feature also functions as expected. However, Agent Mode is still not working, and the MCP Servers are not connecting.
Would it be accurate to describe Edit Mode as a sort of “mini Agent Mode”?
Hi, I’ve been using cursor both at home and work. At home everything works perfectly but at work behind a proxy (Zscaler), only the “Ask mode” and “Edit mode” was working in v0.47.8 (Using HTTP1.1, since all HTTP2 requests are blocked by our proxy)
Upgrading to the latest “v0.48.6”, only the “Manual mode” works so I downgraded it.
Would it be possible to have the agent mode works on HTTP1.1?
It looks like they’re doing their best to find a solution, but with every version upgrade, they end up taking a step backward. So, as you mentioned, you had to downgrade.
When I was on v46.x, I was told to upgrade to the next version because they might have found a solution to the Zscaler issue. Now, at v48.6, there’s still no direct fix. They suggested that I ask my Corporate IT to whitelist a bunch of domains—something I’m sure they’ll never do, especially considering that Cursor is only “tolerated” because VS Code is officially allowed. I only use it under the pretext of a “VS Code Extension,” which isn’t entirely accurate since Cursor is technically a standalone application.
same connection issue with the zscaler with the new version but when i downgraded to old version 0.46 the ask is working and agent it not working please @cursorbot find the solution what is the use of upgrading to pro?
Regretfully, I also just started using Copilot, which now works natively the same way Cursor does. I don’t know how Copilot worked before. I thought it was just an extension like any other. But now it’s 1:1 like Cursor. You just need to enable it in the settings and 'toggle secondary sidebar’and there you have it. No issues with Zscaler."