{"version":"2.1.281","anchor":"more-windows-environment-variables-are-now-in-the-settings-e","canonical_anchor":"more-windows-environment-variables-are-now-in-the-settings-e","heading":"More Windows environment variables are now in the settings env-var set","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/more-windows-environment-variables-are-now-in-the-settings-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### More Windows environment variables are now in the settings env-var set\n\nMore Windows environment variables, such as `SYSTEMROOT`, `COMSPEC` and `PSMODULEPATH`, now get special handling when set in settings `env`\n\n**Unclear.** The finding does not say what the special handling does to these variables.\n\n**What**\n\nThe `env` section of a settings file sets environment variables for Claude Code. Claude Code handles some of these variables specially. More Windows variables are now in that group, including:\n\n- `SYSTEMROOT` and `WINDIR`\n\n- `COMSPEC`\n\n- `PROGRAMFILES` and `LOCALAPPDATA`\n\n- `PATHEXT`\n\n- `PSMODULEPATH`\n\n- `HOMESHARE`\n\n- the `ONEDRIVE*` variables\n\nThe same group also decides which `env` keys from project or local settings are reported when a bundle is uploaded to the cloud.\n\n**Why**\n\nIf your settings set any of these Windows variables, Claude Code now treats them differently from before."}