Follow Discord
Sweep 23 Oct 2026 · 21:48Z Build v2.1.310 529 read Stable v2.1.308 Latest v2.1.310 Next v2.1.310 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.310 ·

WebSocket and Google sign-in connections are set up differently

WebSocket connections now get their own TLS settings, and the Google sign-in client takes its network options from a shared helper

Under the hood Internal Changes
JSON All of v2.1.310
Under the hoodTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
InternalsArea: what it touches
Internal ChangesKind: in v2.1.310,
Internal ChangesSection of the release

Unclear What connection options the shared helper supplies, and so what changes for Google sign-in users, is not stated.

What

Two kinds of network connection changed how they are set up:

  • WebSocket connections (a long-lived two-way connection) now pass TLS settings, which control encrypted connections.
  • The Google sign-in client now takes its connection options from a shared helper instead of one fixed setting.
Why

This may change how proxies and encrypted connections are handled when using Google Vertex or Google sign-in.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat connection options the shared helper supplies, and so what changes for Google sign-in users, is not stated.

See this entry in the whole of v2.1.310 →

Feedback