{"version":"2.1.283","anchor":"settings-warning-explains-values-replaced-with-their-restric","canonical_anchor":"settings-warning-explains-values-replaced-with-their-restric","heading":"Settings warning says when a value was replaced rather than skipped","tier":"notice","area":"Configuration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/settings-warning-explains-values-replaced-with-their-restric","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Settings warning says when a value was replaced rather than skipped\n\nThe startup settings warning now says some values were replaced with their stricter reading, where before it said all were skipped\n\n**What**\n\nWhen a settings file contains values Claude Code cannot use, a dialog at startup lists them. Some of those values are locks, settings meant to restrict something. An invalid lock is not ignored; it is treated as its most restrictive value. When the list includes values like that, the dialog now says: \"The values listed above were replaced with their restrictive reading or skipped as noted; the rest of the file is in effect.\" Before, it always said every listed value was skipped.\n\n**Why**\n\nThe old message was wrong for these values. They are still in force, in their strictest form, so reading \"skipped\" could leave you expecting a restriction had gone away when it had not.\n\n- Area: Configuration\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}