[DOCS] Inconsistent Syntax for NO_PROXY in Network Configuration

Documentation Type

Unclear/confusing documentation

Documentation Location

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

Section/Topic

Proxy configuration section regarding the NO_PROXY environment variable.

Current Documentation

The documentation currently provides two different formats for the same variable:

# 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"

What's Wrong or Missing?

The documentation provides conflicting examples (space-separated vs. comma-separated) without indicating which format is the primary standard for Claude Code's environment.

Since Claude Code is a Node.js-based application, it typically relies on underlying libraries (like undici or standard fetch) which usually follow the industry standard of comma-separated values for NO_PROXY. Providing both without a "recommended" label or clarification on compatibility may lead users to use the space-separated format in environments where it is not supported, causing proxy bypass failures.

Suggested Improvement

Clarify which format is preferred and verify if both are actually supported by the Claude Code binary.

Suggested Text:

Note on NO_PROXY Syntax: While some systems allow space-separated values, the industry standard and preferred format for Claude Code is a comma-separated list. To ensure maximum compatibility with the underlying Node.js networking stack, use commas: export NO_PROXY="localhost,127.0.0.1,example.com"

Impact

High - Prevents users from using a feature

Additional Context

• Related Documentation: https://code.claude.com/docs/en/network-config
• Technical Context: Most modern Unix tools and Node.js networking agents (such as proxy-agent or undici) strictly expect commas. Examples from other major projects (like Docker or Kubernetes) prioritize comma-separated strings for this specific variable to avoid parsing errors.