{"version":"2.1.299","anchor":"settings-env-filtering-tracks-a-dropped-git-key","canonical_anchor":"settings-env-filtering-tracks-a-dropped-git-key","heading":"Claude Code notes when a git-related variable is dropped from a settings file","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/settings-env-filtering-tracks-a-dropped-git-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code notes when a git-related variable is dropped from a settings file\n\nWhen applying environment variables from settings files, Claude Code now records when a git-related key was dropped and reads each layer's own block\n\n**Unclear.** Which git-related key gets dropped, and whether it is one a reader might set on purpose, is not stated.\n\n**What**\n\nSettings files can contain an `env` block, which is a list of environment variables (named values passed to programs) that Claude Code applies when it starts. Settings come in layers, such as your personal settings and a project's settings, and Claude Code filters each layer's `env` block before using it.\n\nTwo things changed in that step:\n\n- Claude Code now records when a git-related key was dropped from one of the layers during filtering.\n\n- Each layer is now filtered using its own `env` block, where before the step read a different one.\n\n**Why**\n\nThis may change which environment variables from your settings files actually take effect, especially ones related to git.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}