{"version":"2.1.248","anchor":"project-settings-can-no-longer-redirect-your-config-director","canonical_anchor":"project-settings-can-no-longer-redirect-your-config-director","heading":"Project settings can no longer redirect your config directory","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/project-settings-can-no-longer-redirect-your-config-director","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Project settings can no longer redirect your config directory\n\nA project's settings can no longer redirect CLAUDE_CONFIG_DIR to somewhere else.\n\n**What**\n\nIf a checked-out project's settings, or its local settings, set `CLAUDE_CONFIG_DIR` to somewhere other than the directory already in use, that override is now detected and refused rather than followed. Without such an override, the usual config directory is used.\n\n**Details**\n\n- Both the shared project settings file and the untracked local one are checked.\n- Comparison is on the resolved path, so a differently written path to the same directory is not treated as an override.\n\n**Evidence**\n\n`CLAUDE_CONFIG_DIR`\n\n- Area: Settings\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}