{"version":"2.1.277","anchor":"settings-alias-handling-gains-an-explicit-unset-via-null-m","canonical_anchor":"settings-alias-handling-gains-an-explicit-unset-via-null-m","heading":"Settings alias handling gains an explicit 'unset via null' mode","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/settings-alias-handling-gains-an-explicit-unset-via-null-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Settings alias handling gains an explicit 'unset via null' mode\n\nSetting a renamed settings key's old alias to null can now explicitly reset it instead of just being dropped\n\n**What**\n\nSome settings keys have both a current name and an older alias. Previously, setting the alias to `null` had one behavior. Now, when a special mode called `loneNullAlias === 'rename'` applies and the current (canonical) key has no value set, setting the alias to `null` is treated as an explicit reset: Claude Code writes `null` onto the canonical key before removing the alias. In other cases, the alias is just dropped as before.\n\n**Why**\n\nThis lets a `null` on an old setting name still express 'clear this setting' after it has been renamed, instead of that intent getting lost.\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}