Fixed
The CLI now works on corporate networks that send traffic through an HTTP proxy or inspect HTTPS
If your network routes outbound traffic through an HTTP proxy or uses TLS inspection (common in corporate environments), the CLI previously failed to connect. It now respects standard proxy environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY) and accepts custom CA certificates, so you can deploy and develop without connectivity errors behind a corporate firewall.