[DOCS] Contradictory statements regarding SOCKS proxy support

Documentation Type

Missing documentation (feature not documented)

Documentation Location

• https://code.claude.com/docs/en/network-config#proxy-configuration - https://code.claude.com/docs/en/settings#sandbox-settings

Section/Topic

• The Proxy configuration section on the Network Config page. - The Sandbox settings table on the Settings page.

Current Documentation

On the Network Config page, under the Proxy configuration section, the documentation explicitly states:

"Claude Code does not support SOCKS proxies."

However, on the Settings page, under the "Sandbox settings" table, the following configuration key is listed:

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

What's Wrong or Missing?

There is a direct contradiction between these two pages.

1. One page categorically states that SOCKS proxies are not supported.
2. The other page documents specific configuration options (network.socksProxyPort) for using a SOCKS5 proxy.

It is unclear if SOCKS proxies are supported entirely, supported only for the Sandbox feature but not for general API traffic, or if the functionality was recently added/removed and one of the pages is outdated.

Suggested Improvement

Please clarify the scope of SOCKS proxy support.

Scenario A: SOCKS is supported only for the Sandbox
If SOCKS is only supported for the sandboxed bash environment but not for the Claude Code client's connection to the API, please update the Network Config page to say:

"Claude Code does not support SOCKS proxies for API connections, though they are supported within the Sandbox configuration (see Settings)."

Scenario B: SOCKS is fully supported
Remove the note "Claude Code does not support SOCKS proxies" from the Network Config page and provide the environment variable or setting to configure it globally.

Scenario C: SOCKS is not supported
Remove the network.socksProxyPort entry from the Settings reference if it is non-functional.

Impact

High - Prevents users from using a feature

Additional Context

This confusion affects users trying to configure Claude Code behind corporate firewalls that utilize SOCKS proxies. Clarifying whether the proxy support applies to the agent's traffic vs. the client's traffic is essential.