{"version":"2.1.300","anchor":"settings-env-handling-launch-credential-tracking-and-person","canonical_anchor":"settings-env-handling-launch-credential-tracking-and-person","heading":"Settings now track which environment values a person wrote","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/settings-env-handling-launch-credential-tracking-and-person","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Settings now track which environment values a person wrote\n\nClaude Code now records which environment values in settings a person wrote, and works out a launch credential from the environment it started in\n\n**Unclear.** What this changes for someone who sets environment values in their settings is not stated.\n\n**What**\n\nEnvironment values are named settings, such as variables, that Claude Code reads when it starts. Claude Code's handling of environment values that come from settings files has changed:\n\n- It now records which of those values a person wrote.\n\n- It works out a launch credential from the environment it was started in.\n\n- It checks whether OpenTelemetry settings take priority. OpenTelemetry is a standard for sending monitoring data.\n\nBefore, it tracked only the environment values that settings offered.\n\n**Why**\n\nThis affects how Claude Code decides where an environment value came from, especially in hosted sessions.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}