{"version":"2.1.248","anchor":"spawned-git-and-shell-helpers-get-only-an-explicit-environme","canonical_anchor":"spawned-git-and-shell-helpers-get-only-an-explicit-environme","heading":"Spawned git and shell helpers get only an explicit environment","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/spawned-git-and-shell-helpers-get-only-an-explicit-environme","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Spawned git and shell helpers get only an explicit environment\n\nSpawned git and shell helpers no longer inherit your full environment, only what Claude Code builds.\n\n**What**\n\nThree process-spawn sites no longer pass the parent's full environment to the child; each child now receives only the variables Claude Code builds for it.\n\n**Details**\n\n- New fixed environment sets for git: one setting `GIT_LITERAL_PATHSPECS` to \"1\", a variant setting it to \"0\", and a config-isolation set including `GIT_CONFIG_NOSYSTEM: \"1\"`.\n- These replace an older space-separated string listing the same variable names.\n- Unconditional at those call sites.\n\n**Evidence**\n\n`extendEnv: !1`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}