{"version":"2.1.281","anchor":"windows-env-var-case-normalisation-now-covers-claude-config","canonical_anchor":"windows-env-var-case-normalisation-now-covers-claude-config","heading":"Windows env-var case normalisation now covers CLAUDE_CONFIG_DIR","tier":"notice","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/windows-env-var-case-normalisation-now-covers-claude-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Windows env-var case normalisation now covers CLAUDE_CONFIG_DIR\n\nOn Windows, a CLAUDE_CONFIG_DIR variable written in any upper or lower case is now recognised under its standard name\n\n**What**\n\nOn Windows, Claude Code renames environment variables to their standard spelling when they are written in a different case. Environment variables are named settings passed in from your system or shell. That list now includes `CLAUDE_CONFIG_DIR`, so a variable named `claude_config_dir`, for example, is treated as `CLAUDE_CONFIG_DIR`.\n\n**Why**\n\nWindows does not care about upper or lower case in these names. If you set this variable in a different case, Claude Code now picks it up instead of missing it.\n\n- Area: Windows\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}