Enterprise network configuration
Configure Claude Code for enterprise environments with proxy servers, custom Certificate Authorities (CA), and mutual Transport Layer Security (mTLS) authentication.
Claude Code supports various enterprise network and security configurations through environment variables. This includes routing traffic through corporate proxy servers, trusting custom Certificate Authorities (CA), and authenticating with mutual Transport Layer Security (mTLS) certificates for enhanced security.
Proxy configuration
Environment variables
Claude Code respects standard proxy environment variables:
# HTTPS proxy (recommended)
export HTTPS_PROXY=https://proxy.example.com:8080
# HTTP proxy (if HTTPS not available)
export HTTP_PROXY=http://proxy.example.com:8080
# 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"
# Bypass proxy for all requests
export NO_PROXY="*"
Basic authentication
If your proxy requires basic authentication, include credentials in the proxy URL:
export HTTPS_PROXY=http://username:password@proxy.example.com:8080
CA certificate store
By default, Claude Code trusts both its bundled Mozilla CA certificates and your operating system's certificate store. Reading the OS store requires a runtime with tls.getCACertificates: the native installer always has it, and npm installs need Node 22.15 or later. On older Node versions, only the bundled set and NODE_EXTRA_CA_CERTS apply. Enterprise TLS-inspection proxies such as CrowdStrike Falcon and Zscaler work without additional configuration when their root certificate is installed in the OS trust store and the runtime can read it.
CLAUDE_CODE_CERT_STORE accepts a comma-separated list of sources. Recognized values are bundled for the Mozilla CA set shipped with Claude Code and system for the operating system trust store. The default is bundled,system.
To trust only the bundled Mozilla CA set:
export CLAUDE_CODE_CERT_STORE=bundled
To trust only the OS certificate store:
export CLAUDE_CODE_CERT_STORE=system
Custom CA certificates
If your enterprise environment uses a custom CA, configure Claude Code to trust it directly:
export NODE_EXTRA_CA_CERTS=/path/to/ca-cert.pem
mTLS authentication
For enterprise environments requiring client certificate authentication:
# Client certificate for authentication
export CLAUDE_CODE_CLIENT_CERT=/path/to/client-cert.pem
# Client private key
export CLAUDE_CODE_CLIENT_KEY=/path/to/client-key.pem
# Optional: Passphrase for encrypted private key
export CLAUDE_CODE_CLIENT_KEY_PASSPHRASE="your-passphrase"
Claude Code reads the certificate and key files at startup and re-reads them each time it applies settings, including when settings change during a session. To rotate the certificate and key, replace the files at the same paths.
In cloud sessions, the hosting environment manages the connection to the API, so Claude Code ignores the following variables when they come from a settings file env block:
CLAUDE_CODE_CLIENT_CERTCLAUDE_CODE_CLIENT_KEYCLAUDE_CODE_CLIENT_KEY_PASSPHRASENODE_EXTRA_CA_CERTSNODE_TLS_REJECT_UNAUTHORIZEDCLAUDE_CODE_OAUTH_SCOPES
Claude Code notes each ignored key in the session's debug log.
Apply network settings to background agents
Background agents don't run inside the terminal that dispatched them. A per-user supervisor process starts on demand, outlives your shell, and hosts every claude agents, --bg, and /background session. See How background sessions are hosted. This changes how the configuration on this page reaches those sessions.
Set network variables in settings, not the shell
The supervisor is one process shared by every terminal. It inherits the environment of whichever shell starts it first, and an OS-installed supervisor receives no shell environment at all. If you export a proxy, CA path, or mTLS variable only in your shell, it reaches background agents when that shell happened to cold-start the supervisor, and silently doesn't when a different shell did.
Put the same variables in the env block of ~/.claude/settings.json or managed settings instead. Every variable on this page can be set there, and settings are the only configuration that reaches every background session on every machine.
Configure a corporate launcher as a setting
Some organizations require every Claude Code process to start through a corporate launcher that applies sandboxing, network controls, or credential injection. The supervisor and its workers start Claude Code from a fixed path rather than by looking up claude on PATH, so every background agent bypasses a wrapper you place earlier on PATH.
Set the processWrapper setting to prefix the supervisor, its workers, and the other background processes listed under What the launcher covers with your launcher. The equivalent CLAUDE_CODE_PROCESS_WRAPPER environment variable takes precedence when both are set, and it is subject to the same rule: deliver it through managed settings or ~/.claude/settings.json, not a shell export. Run Claude Code behind a corporate launcher covers the contract the launcher must satisfy, what it does and doesn't reach, and how to roll it out.
Network access requirements
Claude Code requires access to the following URLs. Allowlist these in your proxy configuration and firewall rules, especially in containerized or restricted network environments.
| URL | Required for |
|---|---|
api.anthropic.com |
Claude API requests, including the WebFetch domain safety check, feature flag fetches, and telemetry event logging |
claude.ai |
claude.ai account authentication |
claude.com |
claude.ai account sign-in opens a claude.com page in the browser, which redirects to claude.ai; pre-approved WebFetch documentation lookups also reach this host from the CLI |
platform.claude.com |
Anthropic Console account authentication. OAuth token exchange, refresh, and revocation also go to this host for claude.ai accounts, so both Console and claude.ai sign-ins require it |
mcp-proxy.anthropic.com |
MCP connectors from claude.ai, including connectors an organization administrator configures. Connector traffic routes through this proxy; connectors are enabled by default for claude.ai-authenticated users. To disable, set ENABLE_CLAUDEAI_MCP_SERVERS=false or the disableClaudeAiConnectors setting |
downloads.claude.ai |
Plugin executable downloads; native installer, native auto-updater, and update version checks |
storage.googleapis.com |
Install counts and plugin metadata shown in /plugin. Signed artifact uploads try this host first; publishing falls back to api.anthropic.com when it is blocked |
storage.googleapis.com |
{/* max-version: 2.1.115 */}Native installer and native auto-updater on versions prior to 2.1.116 |
bridge.claudeusercontent.com |
Claude in Chrome extension WebSocket bridge |
raw.githubusercontent.com |
Changelog feed for /release-notes and the release notes shown after updating |
http-intake.logs.us5.datadoghq.com |
Operational telemetry events, sent only when the CLI uses the Anthropic API directly, never for Amazon Bedrock, Google Cloud's Agent Platform, or Microsoft Foundry. Optional: disable with DISABLE_TELEMETRY or DO_NOT_TRACK |
browser-intake-us5-datadoghq.com |
Operational error reports, sent when the CLI uses the Anthropic API directly and a server-side rollout gate enables them. Optional: disable with DISABLE_ERROR_REPORTING or DISABLE_TELEMETRY; see Telemetry services |
formulae.brew.sh |
Update version checks on Homebrew installs. Other install methods don't contact this host |
code.claude.com |
Claude Code documentation lookups by the built-in claude-code-guide agent and pre-approved WebFetch requests. Blocking this host only affects documentation lookups |
If you install Claude Code through npm or manage your own binary distribution, end users don't need the native installer and auto-updater uses of downloads.claude.ai, but npm and bun installs need their package registry, registry.npmjs.org, unless your organization mirrors it. The other uses in the table apply regardless of install method.
The two Datadog intake hosts carry only optional operational telemetry, and setting CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC disables both. Sessions on third-party providers never send to these hosts, even when a platform sets CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST and telemetry metrics default on. See Telemetry services for everything Claude Code sends and how to disable it before finalizing your allowlist.
When using Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, or a signed-in Claude apps gateway session, model traffic and authentication go to your provider or gateway instead of api.anthropic.com, claude.ai, or platform.claude.com. The WebFetch tool still calls api.anthropic.com for its domain safety check unless you set skipWebFetchPreflight: true in settings.
When routing through an LLM gateway with ANTHROPIC_BASE_URL, the fast mode availability check still calls api.anthropic.com rather than the gateway base URL. The check does honor a configured HTTP proxy, so where a network block is the cause, an allowlist entry for api.anthropic.com in the proxy is the fix. A network block fails the check only where the host is unreachable even through the proxy, and fast mode then reports a connectivity error. The same connectivity error appears when the check presents a gateway-issued credential that Anthropic rejects; allowlisting doesn't help there, since nothing is blocked. See use fast mode behind proxies and LLM gateways for the variables that restore it.
Claude Code on the web and Code Review connect to your repositories from Anthropic-managed infrastructure. If your GitHub Enterprise Cloud organization restricts access by IP address, enable IP allow list inheritance for installed GitHub Apps. The Claude GitHub App registers its IP ranges, so enabling this setting allows access without manual configuration. To add the ranges to your allow list manually instead, or to configure other firewalls, see the Anthropic API IP addresses.
For self-hosted GitHub Enterprise Server instances behind a firewall, allowlist the same Anthropic API IP addresses so Anthropic infrastructure can reach your GHES host to clone repositories and post review comments.
Desktop and claude.ai
The preceding table covers the standalone CLI. The Claude Desktop app and claude.ai in a browser load their application code and user content from additional Anthropic CDN hosts, including assets-proxy.anthropic.com and the *.claudeusercontent.com origins that serve artifacts. Allowing claude.ai while blocking those hosts produces a blank page rather than an error. See network access requirements on the Desktop page.