A project's settings can no longer redirect CLAUDE_CONFIG_DIR to somewhere else.
What's wrong with this entry?
If 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.
- Both the shared project settings file and the untracked local one are checked.
- Comparison is on the resolved path, so a differently written path to the same directory is not treated as an override.
CLAUDE_CONFIG_DIR
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Org public-projects memory kind dropped
Both mention config
-
v2.1.239
Remote Control bridge sessions reject foreign --mcp-config entries
Both mention config
-
v2.1.239
Remote sessions drop disallowed --mcp-config servers instead of failing the run
Both mention config