{"version":"2.1.273","anchor":"settings-not-applied-warning-now-names-the-source-file-and","canonical_anchor":"settings-not-applied-warning-now-names-the-source-file-and","heading":"Settings 'not applied' warning now names the source file and lists all affected keys","tier":"notice","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/settings-not-applied-warning-now-names-the-source-file-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Settings 'not applied' warning now names the source file and lists all affected keys\n\nClaude Code now warns by name when settings keys are set in a managed-settings file that doesn't actually apply to them\n\n**What**\n\nClaude Code can now detect when settings keys are configured in a managed-settings file whose source doesn't apply for those particular keys. When this happens, it shows a new warning that names the specific source file, lists every offending key, and tells the user to either remove them or move them to a settings source that does apply, pointing to `\/status` (the Settings interface, on the Status tab) to see the list of settings sources.\n\n**Why**\n\nThis surfaces settings that are silently being ignored because they're defined in the wrong place, so users can find and fix misconfigured settings instead of wondering why a setting isn't taking effect.\n\n- Area: Settings\n- Names: `\/status`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}