{"version":"2.1.317","anchor":"added-folder-plugins-follow-setting-sources","canonical_anchor":"added-folder-plugins-follow-setting-sources","heading":"Settings files in added folders can follow your chosen setting sources","tier":"notice","area":"Internals","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/added-folder-plugins-follow-setting-sources","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Settings files in added folders can follow your chosen setting sources\n\nClaude Code can now skip settings files in added folders when the setting sources they belong to are not enabled\n\n**Unclear.** It is not clear whether this filtering is in use yet or depends on a switch.\n\n**What**\n\nClaude Code reads settings from several layers, such as project settings and local settings. It now has a rule linking each settings file to its layers:\n\n- `settings.json` belongs to project settings\n\n- `settings.local.json` belongs to both project settings and local settings\n\nA file is kept only when all of its layers are enabled, and others are left out.\n\n**Why**\n\nPlugins and settings from folders added with `--add-dir` may now respect the layers you pick with `--setting-sources`.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}