# Claude Code settings

Verify the actual client, environment and every relevant launch path.

Updated: 2026-11-05
Canonical: https://shortant.ai/en/guides/claude-code/

Adapted from Public Network Protection Guide 3.0.1. Read-only review first; no universal executable configuration is supplied.

## Proxy configuration is client-specific

Current Claude Code documentation describes HTTP_PROXY, HTTPS_PROXY and NO_PROXY for the CLI; these values are read at startup. The CLI documentation does not describe SOCKS as a supported proxy transport. Check the installed version before changing values.

Inspect uppercase/lowercase conflicts and bypass scope without publishing real endpoints. Do not assume GUI launches, IDE tasks, SDK children or remote sessions inherit a terminal setting.

## Preserve TLS and deployment mode

Keep certificate and hostname verification. For TLS failures, inspect time, DNS, certificate chain and the actual route; do not disable validation to make a check pass.

Desktop managed configuration and third-party-provider modes have their own applicability. Keep the existing provider/account mode; a key documented for one mode does not establish support in another. Local callback and WebSocket paths also require their own scope review.

## Read back and recheck

After an approved, minimal change, verify the actual launched process and independently observed traffic. Repeat relevant checks after client updates, path changes, filter updates and new launch entries. A successful website scan is not acceptance of the CLI boundary.

## Sources and scope

- [Claude Code network configuration](https://code.claude.com/docs/en/network-config)

Independent educational adaptation; vendor documents retain their owners’ rights. Check the installed version and applicability. Browser scores do not verify local isolation, account access or ban risk.