Improvements / v2.1.323
Stop using ALL_PROXY for policy requests
CHANGELOG · original
Changed organization settings and policy requests to no longer use a proxy set only by ALL_PROXY; set HTTPS_PROXY if your network needs a proxy for them Open official changelog ↗ Documentation
Documentation excerpt
Environment variables
Claude Code respects standard proxy environment variables. In Claude Desktop sessions where the app manages the provider connection, Claude Code reads them only from managed settings and ~/.claude/settings.json; see mTLS authentication for the scope rules.
# HTTPS proxy (recommended)
export HTTPS_PROXY=https://proxy.example.com:8080
# HTTP proxy (if HTTPS not available)
export HTTP_PROXY=http://proxy.example.com:8080
# Bypass proxy for specific requests - space-separated format
export NO_PROXY="localhost 192.168.1.1 example.com .example.com"
# Bypass proxy for specific requests - comma-separated format
export NO_PROXY="localhost,192.168.1.1,example.com,.example.com"
# Bypass proxy for all requests
export NO_PROXY="*"
Lowercase variants also work, and Claude Code uses the first one that's set in the order https_proxy, HTTPS_PROXY, http_proxy, HTTP_PROXY.
Claude Code never sends its WebSocket connections to localhost, ::1, or 127.0.0.0/8 through the proxy, so you don't need a loopback entry in NO_PROXY for them.
[!NOTE]
Claude Code does not support SOCKS proxies.
Documentation snapshot · 2026-11-20