Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.223 Home All releases ←olderv2.1.222 v2.1.224newer→
Claude Code v2.1.223

OAuth refresh telemetry gained a context tag

Under the hood
Useful1 Signal0
Auth

Login token refresh failures are now labelled with the action that triggered them.

What

Token refresh failures can now be attributed to the flow that triggered them, and failures with a known context no longer emit the generic failure status.

Details
  • tengu_oauth_token_refresh_failure includes a context property when the refresh was made on behalf of a named flow.
  • Plugin scope expansion passes telemetryContext: "plugins_scope_expansion".
  • The generic "oauth_refresh_request_failed" status is only recorded when no context is present.
Evidence

tengu_oauth_token_refresh_failure

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.223 →