{"version":"2.1.295","anchor":"settings-panel-auto-update-channel-and-notification-changes","canonical_anchor":"settings-panel-auto-update-channel-and-notification-changes","heading":"Update channel and notification settings in \/config are checked before saving","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/settings-panel-auto-update-channel-and-notification-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Update channel and notification settings in \/config are checked before saving\n\nChanges to the update channel and notification settings in `\/config` now go through one shared check, which rejects unknown values\n\n**What**\n\nIn the settings panel opened with `\/config`, changes to these settings now pass through one shared step that checks them before saving:\n\n- `autoUpdatesChannel`, the release channel Claude Code updates from\n\n- the notification channel, which decides how Claude Code notifies you\n\n- the notification on\/off toggles\n\nIf the notification channel would be set to a value that row does not recognise, the change is refused with a message beginning \"Notifications channel doesn't accept\". Turning on automatic updates, switching channel and downgrading now all use the same saving step. Previously each of these wrote your user settings directly.\n\n**Why**\n\nSettings changed from `\/config` are now validated and recorded in one consistent way, so a bad notification value is refused instead of being saved.\n\n- Area: Settings\n- Names: `\/config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}