{"version":"2.1.268","anchor":"env-var-telemetry-allowlist-and-a-no-op-stub-added-near-it","canonical_anchor":"env-var-telemetry-allowlist-and-a-no-op-stub-added-near-it","heading":"Env-var telemetry allowlist and a no-op stub added near it","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/env-var-telemetry-allowlist-and-a-no-op-stub-added-near-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Env-var telemetry allowlist and a no-op stub added near it\n\nTelemetry now only logs recognized CLAUDE_CODE_*\/ANTHROPIC_* env var names by name, bucketing the rest as 'other'\n\n**What**\n\nA new allowlist of about 30 named `CLAUDE_CODE_*` and `ANTHROPIC_*` environment variables is now used when logging which environment variables are set: names on the list are reported as-is, while any other environment variable name is bucketed and logged simply as \"other\". An unrelated no-op function was added nearby in the same change but does nothing.\n\n**Why**\n\nThis keeps diagnostics and telemetry from recording arbitrary, potentially sensitive environment variable names that happen to start with those prefixes, only known\/expected variable names are reported individually.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}