Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.281 ·

Remote managed settings fetch telemetry gains auth diagnostics

The remote managed-settings fetch event now also reports how sign-in went, including token source, refresh results and server errors

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

The tengu_remote_settings_fetch telemetry event now also records details about authentication, meaning how Claude Code proved who you are when it fetched settings. The new fields are:

  • auth_type, token_source and credential_origin (either stored_login or injected_token)
  • the outcomes of any token refresh
  • retried_after_401, which shows whether the request was retried after the server said it was not authorized
  • the server's error type and code, and server_auth_denial
  • credential_state, errno and ms_since_startup
  • api_key_prefix, sent only when you are signed in with an API key
Why

When remote managed settings fail to arrive, these fields make it possible to tell whether sign-in was the cause and where it went wrong. If you use an API key, note that the start of it is included in this event.

See this entry in the whole of v2.1.281 →

Feedback