Claude Code v2.1.319 ·
An expired Cloud gateway sign-in now pauses telemetry and settings checks
With an expired Cloud gateway sign-in, telemetry is not sent and you are told to run /login, and background settings checks are skipped
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
LLM GatewayArea: what it touches
ImprovementsKind: in v2.1.319,
ImprovementsSection of the release
What
When your Cloud gateway sign-in has expired, two background jobs stop:
- Telemetry: each batch of usage data that would be sent fails with a message saying it was not sent and asking you to run
/login to reconnect.
- Remote settings: the regular background check for settings managed from elsewhere is skipped.
Why
If you use a Cloud gateway, these messages tell you that your sign-in has lapsed and that /login fixes it.
See this entry in the whole of v2.1.319 →
