Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.319 ·

CLAUDE_CODE_PROXY_RESOLVES_HOSTS lets a proxy look up names your machine cannot

With CLAUDE_CODE_PROXY_RESOLVES_HOSTS set, websocket connections to names that fail to look up locally are left to the proxy instead of failing

Group of 2 Use it now Notable New Features
JSON All of v2.1.319
Use it nowTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
InternalsArea: what it touches
New FeaturesKind: in v2.1.319,
What probably matters to youSection of the release

What

A proxy is a go-between server that Claude Code can send its network traffic through. CLAUDE_CODE_PROXY_RESOLVES_HOSTS is an environment variable, a setting passed to Claude Code from your shell. It is now listed with the other proxy variables, such as HTTPS_PROXY, NO_PROXY, CLAUDE_CODE_HTTP_PROXY and CLAUDE_CODE_HTTPS_PROXY.

When it is set and your machine cannot look up a server name (the lookup fails with EAI_AGAIN or ENOTFOUND), a websocket connection, a long-lived two-way link to a server, is now left to the proxy to resolve. Before, Claude Code stopped with a "could not resolve" error. Some names are never handed over:

  • names that mean your own machine (loopback)
  • names that point at cloud metadata services
  • names with an empty part, such as two dots in a row

Why

On networks where only the proxy can look up outside names, such as sandboxed or proxy-only setups, these connections can now go through instead of failing at the name lookup.

Read from

See this entry in the whole of v2.1.319 →

Feedback