{"version":"2.1.290","anchor":"project-settings-env-var-guard-now-allows-pinned-values","canonical_anchor":"project-settings-env-var-guard-now-allows-pinned-values","heading":"Project settings can now set some keys, but only to one fixed value","tier":"notice","area":"Settings","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/project-settings-env-var-guard-now-allows-pinned-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Project settings can now set some keys, but only to one fixed value\n\nSome settings keys can now be set by a project's settings only to one specific value, with a warning when a project tries anything else\n\n**Unclear.** Which keys are limited to a single value is not stated.\n\n**What**\n\nA project's settings are the settings file stored inside a project folder, which anyone who shares that folder can edit. Claude Code already ignored some keys there, with a warning saying either that the key can only come from the environment or that project settings cannot set it.\n\nThere is now a third case: a key that a project's settings may set only to one specific value. If a project tries a different value, the warning says that a project's settings can only set it to that value. Some further keys are also now skipped when they come from project settings.\n\n**Why**\n\nThis draws a finer line around what a shared project folder is trusted to change, instead of an all-or-nothing rule for each key.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}