[DOCS] Network and env-var docs still describe Claude Code as running on a Node.js runtime after v2.1.113

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

The "CA certificate store" section and related guidance that distinguishes the native binary distribution from the "Node.js runtime"

Current Documentation

The docs currently say:

System CA store integration requires the native Claude Code binary distribution. When running on the Node.js runtime, the system CA store is not merged automatically. In that case, set NODE_EXTRA_CA_CERTS=/path/to/ca-cert.pem to trust an enterprise root CA.

And the environment variable reference says:

CLAUDE_CODE_CERT_STORE ... Default is bundled,system. The native binary distribution is required for system store integration. On the Node.js runtime, only the bundled set is used regardless of this value

The setup guide also still frames npm as a separate install mode without explaining the new execution model:

npm installation is deprecated. The native installer is faster, requires no dependencies, and auto-updates in the background. Use the native installation method when possible.

If you need npm installation for compatibility reasons, you must have Node.js 18+ installed. Install the package globally:

npm install -g @anthropic-ai/claude-code

What's Wrong or Missing?

Changelog v2.1.113 says: "Changed the CLI to spawn a native Claude Code binary (via a per-platform optional dependency) instead of bundled JavaScript."

The docs still describe a Node.js-runtime execution model in places that explain TLS and certificate-store behavior. After v2.1.113, that guidance is outdated or at least incomplete because readers are not told how npm-installed Claude Code now behaves relative to the native binary.

That leaves important questions unanswered for enterprise users:

• whether npm installs now use the same system CA store behavior as other native-binary paths
• whether NODE_EXTRA_CA_CERTS is still required specifically for npm installs
• which behavior differences still exist between npm installs and the native installer after the v2.1.113 change

Suggested Improvement

Update the installation and network/TLS docs to explain the current npm execution model after v2.1.113.

Suggested minimum fix:

1. Add a short note in setup explaining that the npm package now launches a platform-specific native Claude Code binary rather than running the CLI as bundled JavaScript.
2. Update network-config and env-vars to replace the generic "Node.js runtime" wording with precise guidance for current npm installs.
3. Explicitly document whether CLAUDE_CODE_CERT_STORE=system works for npm installs after this change, and when NODE_EXTRA_CA_CERTS is still needed.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/network-config | CA certificate store note still contrasts the native binary distribution with a "Node.js runtime" |
| https://code.claude.com/docs/en/env-vars | CLAUDE_CODE_CERT_STORE entry says system store integration requires the native binary distribution |
| https://code.claude.com/docs/en/setup | npm installation is documented, but the post-v2.1.113 native-binary execution model is not explained |
| https://code.claude.com/docs/en/troubleshooting | npm vs native installation troubleshooting may need the same clarified runtime terminology |

Total scope: 4 pages affected

Source: Changelog v2.1.113

Exact changelog entry:

Changed the CLI to spawn a native Claude Code binary (via a per-platform optional dependency) instead of bundled JavaScript