In agent mode, whenever “taking longer than expected” appears, I try to switch the http protocol. If this happens with http/2, I switch to http/1.1; if it’s http/1.1, I switch to http/2. It works for me. I would like to know if cursor supports automatic adjustment of http? Similar to the strategy of “automatically adjusting if there is no reply within 5 seconds”
Hey, thanks for the question. Cursor doesn’t currently auto switch between HTTP/2 and HTTP/1.1, you pick the mode manually in Settings > Network (HTTP Compatibility Mode). “Taking longer than expected” isn’t an error, it’s just a delay indicator, so it doesn’t trigger any protocol fallback by itself.
We’ve considered auto fallback before, but it’s not on the roadmap, so I wouldn’t expect it anytime soon. Your workflow of switching modes manually when requests get stuck is totally valid, especially on corporate networks or VPNs where HTTP/2 streaming can get blocked by proxies.
If this happens often, you can set HTTP/1.1 once in settings and stop switching back and forth. It’s usually more stable on corporate networks, just a bit slower. It’s also worth running Settings > Network > Run Diagnostics to see which protocol works reliably on your network.