{"version":"2.1.285","anchor":"project-settings-can-no-longer-set-some-keys","canonical_anchor":"project-settings-can-no-longer-set-some-keys","heading":"Project settings files are ignored for more keys","tier":"notice","area":"Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/project-settings-can-no-longer-set-some-keys","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Project settings files are ignored for more keys\n\nClaude Code now ignores more keys in a project's settings file, with the same warning to set them in your own or managed settings\n\n**Unclear.** It is not clear which keys are now ignored or under what condition.\n\n**What**\n\nSome settings cannot be set in a project's own settings file, the one shared with everyone who works on that project. Claude Code now drops keys from project settings under an additional condition, so more of them can be ignored there. The warning is the same: the key \"is ignored - project-scoped settings can't set this key. Set it in ~\/.claude\/settings.json or managed settings instead.\"\n\n**Why**\n\nIf you see this warning for a key that used to work in a project settings file, move it to `~\/.claude\/settings.json` or to managed settings.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}