[DOCS] Inconsistent statements regarding SOCKS proxy support in Network Config vs Settings

Documentation Type

Unclear/confusing documentation

Documentation Location

• https://code.claude.com/docs/en/network-config - https://code.claude.com/docs/en/settings

Section/Topic

• network-config.md: The "Proxy configuration" section. - settings.md: The "Sandbox settings" table.

Current Documentation

In network-config.md under the Proxy configuration section:

"Claude Code does not support SOCKS proxies."

In settings.md under the Sandbox settings table:

"network.socksProxyPort SOCKS5 proxy port used if you wish to bring your own proxy. If not specified, Claude will run its own proxy."

What's Wrong or Missing?

The documentation creates a direct contradiction. network-config.md makes a blanket statement that SOCKS proxies are not supported at all. However, settings.md clearly indicates that SOCKS5 is supported specifically for the Sandboxed Bash Tool via the network.socksProxyPort configuration.

While the distinction likely lies between the Agent connection (API traffic requiring HTTPS) and the Sandbox connection (Bash tool traffic allowing SOCKS), the current phrasing in network-config.md is misleading and suggests the entire application cannot utilize SOCKS proxies in any capacity.

Suggested Improvement

Update the note in network-config.md to explicitly distinguish between the main agent connection and the sandbox capabilities.

Suggested text:

"Claude Code agent connections (API traffic) do not support SOCKS proxies and require HTTPS. However, the Sandboxed Bash Tool supports custom SOCKS proxies via the network.socksProxyPort setting configuration."

Impact

High - Prevents users from using a feature

Additional Context

• Severity: Minor (Potential Confusion)
• This distinction is particularly relevant for enterprise users trying to configure isolated environments who might stop reading at "does not support SOCKS proxies" and assume they cannot use their standard sandbox networking configurations.