{"version":"2.1.300","anchor":"new-credential-road-telemetry-and-cloud-launch-credential-ev","canonical_anchor":"new-credential-road-telemetry-and-cloud-launch-credential-ev","heading":"Analytics now note where your sign-in credential came from","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/new-credential-road-telemetry-and-cloud-launch-credential-ev","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Analytics now note where your sign-in credential came from\n\nSome analytics events now record how the credential was supplied, such as an environment variable, a file descriptor or none at all\n\n**What**\n\nClaude Code now works out how the sign-in credential for a session was supplied. It looks at these environment variables:\n\n- `CLAUDE_CODE_OAUTH_TOKEN`, an access token\n\n- `ANTHROPIC_API_KEY`, an API key\n\n- the file descriptor versions of both, where the value is passed through an open file handle instead of the variable itself\n\nThe result is a short label, such as an environment variable, a file descriptor or none. The label is attached to two analytics events: the one sent when Claude Code fetches remote settings, and the one sent about policy limits on the first prompt.\n\nClaude Code also sends a separate event when fetching remote settings begins, but only when it is running in a particular cloud mode.\n\n**Why**\n\nThis is reporting only. It shows which way credentials were provided, not the credentials themselves, and it does not change how you sign in.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}