Claude Code v2.1.310 ·
Gateway requests may now use custom certificate settings
Gateway model discovery and gateway host checks now pass extra connection and certificate options, likely for custom certificate setups
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release
Unclear It is not clear whether custom certificate settings now fully apply to gateway model discovery and managed settings requests.
What
A gateway is a server some organisations put between Claude Code and the model's API. Several changes touch how Claude Code connects to one:
- Looking up available models through the gateway now sends extra connection options.
- The gateway host check now passes CA certificates, the files that tell Claude Code which secure servers to trust.
- Secure connections now build their list of trusted certificates in a different way.
Why
This matters to company users whose network uses its own certificates. Gateway and managed settings requests may now respect that setup.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether custom certificate settings now fully apply to gateway model discovery and managed settings requests.
See this entry in the whole of v2.1.310 →
