{"version":"2.1.265","anchor":"command-line-entrypoint-telemetry-routed-through-new-normali","canonical_anchor":"command-line-entrypoint-telemetry-routed-through-new-normali","heading":"Command-line entrypoint telemetry routed through new normalizer","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/command-line-entrypoint-telemetry-routed-through-new-normali","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Command-line entrypoint telemetry routed through new normalizer\n\nCommand-line entrypoint telemetry now goes through a normalizer instead of reading the raw environment variable\n\n**What**\n\nThe `entrypoint` field sent in telemetry now comes from a normalizing function applied to the entrypoint value, falling back to `\"other\"` if nothing is found. Previously it read the `CLAUDE_CODE_ENTRYPOINT` environment variable directly and fell back to `\"cli\"`.\n\n**Why**\n\nRouting the value through a normalizer and changing the fallback from `\"cli\"` to `\"other\"` likely produces more consistent and accurate entrypoint labels in telemetry, though the finding doesn't specify what the normalizer changes about the value.\n\n- Area: Telemetry\n- Names: `CLAUDE_CODE_ENTRYPOINT`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}