{"version":"2.1.271","anchor":"telemetry-isclaudeaiauth-added-directly-to-env-context-payl","canonical_anchor":"telemetry-isclaudeaiauth-added-directly-to-env-context-payl","heading":"Telemetry: isClaudeAiAuth added directly to env context payload","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/telemetry-isclaudeaiauth-added-directly-to-env-context-payl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Telemetry: isClaudeAiAuth added directly to env context payload\n\nTelemetry now computes isClaudeAiAuth itself for each event instead of reading it from stored session state\n\n**What**\n\nThe code that builds telemetry payloads now computes the `isClaudeAiAuth` value directly at the point each event is sent, rather than reading it from previously stored session state.\n\n**Why**\n\nThis is an internal telemetry accuracy change: computing the value fresh each time should keep it from going stale if the underlying authentication state changes during a session.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}