Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.309 ·

Cloud gateway reconnect at startup now refuses an ended sign-in

At startup, Claude Code skips a saved Cloud gateway connection whose sign-in has ended and tells you to run /login

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

What

A Cloud gateway is a server, often run by an organisation, that Claude Code's requests can be routed through. At startup, Claude Code tries to restore a saved gateway connection. This release adds a check before it does:

  • Claude Code reads the saved sign-in for that gateway from gatewayAllowlistEntries. If an entry exists and no current credential matches it, the gateway is not connected.
  • You see a warning: "Not connected to Cloud gateway ...: the saved sign-in has ended. Run /login. If that is refused, update Claude Code, or ask your administrator which version to use."
  • When a gateway credential is saved, it is now stored together with its allowlist entry for that gateway's address.
  • The existing checks still apply: whether your organisation's settings name another gateway or none, and the TLS certificate fingerprint check. TLS is the encryption used for the connection. The helper that checks the certificate now receives an extra setting.

Before, the restore went straight to the organisation-settings check, with no saved-sign-in check.

Why

If you use a Cloud gateway, Claude Code may now start without connecting to it and ask you to sign in again with /login. If signing in is refused, the message points you to updating Claude Code or asking your administrator which version to use.

See this entry in the whole of v2.1.309 →

Feedback