{"version":"2.1.310","anchor":"env-from-settings-tracked-by-origin-repository-vs-above-t","canonical_anchor":"env-from-settings-tracked-by-origin-repository-vs-above-t","heading":"Telemetry variables reset when no settings file still sets them","tier":"notice","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/env-from-settings-tracked-by-origin-repository-vs-above-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Telemetry variables reset when no settings file still sets them\n\nSettings env is now tracked by whether it came from the repository, and telemetry variables are put back if no settings source still sets them\n\n**What**\n\nSettings files can set environment variables, values that programs read when they start. Claude Code now tracks whether each one came from the repository's own settings or from a source above it. A new step also puts telemetry variables (the OTEL ones, which say where usage data is sent) back to their startup values, or removes them, when no settings source still sets their current value.\n\n**Why**\n\nThis makes it harder for a repository's settings to redirect where telemetry is sent.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}