{"version":"2.1.293","anchor":"env-var-scan-of-settings-files-now-returns-names","canonical_anchor":"env-var-scan-of-settings-files-now-returns-names","heading":"Settings check now lists which environment variables your settings files set","tier":"internal","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/env-var-scan-of-settings-files-now-returns-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Settings check now lists which environment variables your settings files set\n\nA check on your settings files now reports the names of environment variables they set, and treats project settings as their own level\n\n**What**\n\nClaude Code reads your settings files, the configuration files where you can set options including environment variables (named values that programs read when they start). One check on those files used to give only a yes or no answer about whether any file was unreadable or invalid. It now returns more detail:\n\n- The names of the environment variables set in the `env` section of your settings files\n\n- No result at all if any of those files is invalid\n\nThe check also treats project settings, the settings stored with a particular project, as a separate level.\n\n**Why**\n\nClaude Code can now see which environment variables each settings file sets, not only whether the files are valid. That makes it possible to handle variables differently depending on which settings file sets them, such as one belonging to a project.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}