{"version":"2.0.17","anchor":"socks5-proxy-support-in-network-sandbox","canonical_anchor":"socks5-proxy-support-in-network-sandbox","heading":"SOCKS5 Proxy Support in Network Sandbox","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.17\/e\/socks5-proxy-support-in-network-sandbox","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.17","markdown":"### SOCKS5 Proxy Support in Network Sandbox\n\n**What:** Complete SOCKS5 proxy server added alongside existing HTTP proxy for enhanced network sandboxing on Linux and macOS. Provides dual-proxy infrastructure on ports 1080 (SOCKS) and 3128 (HTTP).\n\n**How to use:** Automatic when network sandbox is enabled. The SOCKS proxy is configured via environment variables:\n\n`# Automatically set when sandbox is active ALL_PROXY=socks5h:\/\/localhost:1080` **Details:**\n\n- SOCKS5 server implementation with authentication and connection filtering\n- Unix socket bridges for both HTTP and SOCKS proxies on Linux (`claude-socks-*.sock`, `claude-http-*.sock`)\n- Environment variables automatically configured: `ALL_PROXY`, `all_proxy`, `GIT_SSH_COMMAND`, `FTP_PROXY`, `GRPC_PROXY`, etc.\n- Function `QJ6()` wraps commands with dual proxy setup using socat\n- Parallel initialization of both proxy servers in `HJ6()`\n- **Evidence**: `QJ6() at line 207609`, `Bp2() at line 207346`, `KJ6()` and `HJ6() at line 207225` in v2.0.17 (SOCKS functionality completely absent from v2.0.15; only HTTP proxy existed)"}