{"version":"2.1.314","anchor":"home-settings-seed-claude-config-dir-only-blocks-it-for-man","canonical_anchor":"home-settings-seed-claude-config-dir-only-blocks-it-for-man","heading":"A custom config folder no longer always blocks the home settings seed","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/home-settings-seed-claude-config-dir-only-blocks-it-for-man","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### A custom config folder no longer always blocks the home settings seed\n\nSetting `CLAUDE_CONFIG_DIR` now stops the home settings seed only in managed sessions; elsewhere the seed can now start and take everything\n\n**Unclear.** What the home settings seed copies, and which sessions count as managed, is not stated.\n\n**What**\n\n`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.\n\nNow `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.\n\n**Why**\n\nSessions 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`.\n\n- Area: Settings\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}