Claude Code v2.1.222 ·
Connectivity check rewritten on fetch, with a timeout and proxy awareness
Connection checks now time out properly and record whether your proxy was used.
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
InternalsArea: what it touches
ImprovementsKind: in v2.1.222,
ImprovementsSection of the release
What
The hello-endpoint probe used by the connection diagnostics now runs on fetch with an explicit timeout and reports whether a proxy was involved.
Details
- Uses
AbortSignal.timeout rather than the previous HTTP client, and cancels the response body. - A timed-out probe is reported as a distinct error rather than a generic failure.
- The result records
usedProxy so the failure UI can tell whether a configured proxy was actually in play.
Evidence
usedProxy
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.222 →
