Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeDocsClaude Code CLI 19 Oct 2026
One change · claude-code

Enterprise network configuration changednetwork-config

Nearest release: v2.1.304, published 2 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 19 Oct 2026 22:14 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 20 Oct 2026 18:37 UTC.

Upstream edited
Recorded here
Lines+19added
Lines−19removed
From line 6 where the diff opens
First seen 14 Aug 2026 this site's first read of the page
Recorded edits37to this page, all time

The whole hunk

from line 6, old and new numbered
/
lines
from line 6
66 
77Set these environment variables before you launch Claude Code. Variables exported in your shell are read once at startup, so a running session doesn't pick up later changes to your shell environment.
88 
9<Note>
10 All environment variables shown on this page can also be configured in [`settings.json`](/docs/en/settings).
11</Note>
9> [!NOTE]
10>
11> All environment variables shown on this page can also be configured in [`settings.json`](/docs/en/settings).
1212 
1313## Proxy configuration
1414 
from line 35
3535 
3636Claude Code never sends its WebSocket connections to `localhost`, `::1`, or `127.0.0.0/8` through the proxy, so you don't need a loopback entry in `NO_PROXY` for them.
3737 
38<Note>
39 Claude Code does not support SOCKS proxies.
40</Note>
38> [!NOTE]
39>
40> Claude Code does not support SOCKS proxies.
4141 
4242### Basic authentication
4343 
from line 47
4747export HTTPS_PROXY=http://username:[email protected]:8080
4848```
4949 
50<Warning>
51 Avoid hardcoding passwords in scripts. Use environment variables or secure credential storage instead.
52</Warning>
50> [!WARNING]
51>
52> Avoid hardcoding passwords in scripts. Use environment variables or secure credential storage instead.
5353 
54<Tip>
55 For proxies requiring advanced authentication (NTLM, Kerberos, etc.), consider using an LLM Gateway service that supports your authentication method.
56</Tip>
54> [!TIP]
55>
56> For proxies requiring advanced authentication (NTLM, Kerberos, etc.), consider using an LLM Gateway service that supports your authentication method.
5757 
5858## CA certificate store
5959 
from line 73
7373export CLAUDE_CODE_CERT_STORE=system
7474```
7575 
76<Note>
77 `CLAUDE_CODE_CERT_STORE` has no dedicated `settings.json` schema key. Set it via the `env` block in `~/.claude/settings.json` or directly in the process environment.
78</Note>
76> [!NOTE]
77>
78> `CLAUDE_CODE_CERT_STORE` has no dedicated `settings.json` schema key. Set it via the `env` block in `~/.claude/settings.json` or directly in the process environment.
7979 
8080## Custom CA certificates
8181 
from line 171
171171 
172172Set the [`processWrapper`](/docs/en/settings-reference#processwrapper) setting to prefix the supervisor, its workers, and the other background processes listed under [What the launcher covers](/docs/en/corporate-launcher#what-the-launcher-covers) with your launcher. The equivalent [`CLAUDE_CODE_PROCESS_WRAPPER`](/docs/en/env-vars) 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](/docs/en/corporate-launcher) covers the contract the launcher must satisfy, what it does and doesn't reach, and how to roll it out.
173173 
174<Note>
175 An already-running supervisor keeps the launch configuration it started with. After deploying the launcher setting, run [`claude daemon stop --any`](/docs/en/agent-view#the-supervisor-process) so the next `claude agents` or `--bg` starts a supervisor that honors it.
176</Note>
174> [!NOTE]
175>
176> An already-running supervisor keeps the launch configuration it started with. After deploying the launcher setting, run [`claude daemon stop --any`](/docs/en/agent-view#the-supervisor-process) so the next `claude agents` or `--bg` starts a supervisor that honors it.
177177 
178178## Streaming idle watchdogs
179179 
Feedback