You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SettingsArea: what it touches
ImprovementsKind: in v2.1.314,
ImprovementsSection of the release
Unclear What the home settings seed copies, and which sessions count as managed, is not stated.
What
CLAUDE_CONFIG_DIR is the environment variable that tells Claude Code where to keep its configuration. Claude Code has a step it calls the home settings seed. Before, setting CLAUDE_CONFIG_DIR always stopped that step from starting.
Now CLAUDE_CONFIG_DIR stops it only when the session was admitted as managed. In other sessions the seed goes ahead, and when it starts it takes everything. Setting CLAUDE_CODE_DISABLE_HOME_SETTINGS_SEED still turns the seed off.
Why
Sessions that use a custom config folder could never get the seed before, and now most of them can. If you do not want it, set CLAUDE_CODE_DISABLE_HOME_SETTINGS_SEED.