[Bug] WebSocket connections don't respect proxy environment variables, making remote control unusable behind a proxy

[github-0-searcher]

Problem

In environments where HTTP proxy environment variables (http_proxy, https_proxy, all_proxy, no_proxy) are configured, the Happy CLI can authenticate successfully, but remote control features fail to connect.

Steps to reproduce

1. Set proxy environment variables, e.g. export https_proxy=http://127.0.0.1:7890
2. Run happy claude — authentication succeeds and claudecode runs smoothly in local mode
3. Try to use remote control — connection fails

Expected behavior

Remote control should work through the proxy, just like authentication does.

Actual behavior

Authentication requests go through the proxy (or at least partially work), but WebSocket connections bypass the proxy entirely and try to connect directly, which fails in proxy-only environments.

Environment

• Proxy type: HTTP/HTTPS/SOCKS