Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

MCP connections read SSL_CERT_FILE only when they actually use a proxy

MCP connections now read the SSL_CERT_FILE certificate bundle only when a proxy applies, not whenever HTTPS_PROXY is set

You'll notice Improvements
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
MCPArea: what it touches
ImprovementsKind: in v2.1.311,
ImprovementsSection of the release
What

MCP servers are outside tools Claude Code connects to. When it reaches one through a proxy (a go-between server set with HTTPS_PROXY), it can use a file of trusted certificates named by SSL_CERT_FILE.

Claude Code now first works out whether a proxy applies to the address. It reads the SSL_CERT_FILE bundle only if one does. Before, it read the file whenever HTTPS_PROXY was set.

Why

Addresses you exclude from the proxy with NO_PROXY no longer cause the certificate file to be read.

Read from
Names in the bundleSSL_CERT_FILEHTTPS_PROXY
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up HTTPS_PROXY, on Configuration reference. > On macOS and Windows the Cowork workspace VM is handed a copy of the script when it starts and evaluates it for each request itself; there `myIpAddress()` returns the VM's internal address rather than the device's, so a script that choos… third-party/claude-desktop/configuration see the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up HTTPS_PROXY, on Configuration reference.

See this entry in the whole of v2.1.311 →

Feedback