I am behind companies network and when I use cursor tab with http2 I will have the error: self signed certificate in certificate chain.
I am aware that turn off http2 and use http1.1 will fix the error, but the agent composer functionality only support http2, I want to be able to use it will cursor tab simutaneously, without turning the option on and off all day.
So, I would like to see either a solution to bypass the certificate issue or agent composer with support for http1.1
Thanks!
I’m experiencing the same issue.
I’m also behind a corporate network that uses a self-signed certificate, and Cursor fails to connect due to the “self signed certificate in certificate chain” error. However, in my case, the problem is not limited to HTTP/2 — the network does not work under any HTTP mode when a self-signed certificate is involved.
Disabling HTTP/2 or switching to HTTP/1.1 does not fully resolve the issue for me, and this makes it impossible to use Cursor reliably in my environment. Since Agent Composer only supports HTTP/2, this effectively blocks that functionality entirely.
It would be really helpful to have:
A way to bypass or trust custom/self-signed certificates, or
Proper support for corporate proxy environments, or
Agent Composer support over HTTP/1.1 as an alternative
Right now, Cursor is unusable behind corporate networks with TLS inspection or self-signed certificates, regardless of the HTTP version.