Update channel and notification settings in /config are checked…

Update channel and notification settings in /config are checked before saving

Changes to the update channel and notification settings in /config now go through one shared check, which rejects unknown values

You'll noticeTier: how much it should matter to you

2Useful: my rating, 1 to 5

1Signal: worth watching, 1 to 5

SettingsArea: what it touches

ImprovementsKind: in v2.1.295, 08 Oct 26

ImprovementsSection of the release

What

In the settings panel opened with /config, changes to these settings now pass through one shared step that checks them before saving:

autoUpdatesChannel, the release channel Claude Code updates from
the notification channel, which decides how Claude Code notifies you
the notification on/off toggles

If 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.

Why

Settings changed from /config are now validated and recorded in one consistent way, so a bad notification value is refused instead of being saved.

Read from

Names in the bundle/config

How sure we are

One source agreesOne thing we can check says the same as this entry.

Anthropic's release notes agreeFixed PushNotification saying a push was not sent in claude remote-control sessions right after a phone message, without the /config toggle…

See this entry in the whole of v2.1.295 →

The build it came inv2.1.295

8 Oct 2026 · 429 entries, this one is #162.

Use it now34
You'll notice243
Nothing to try yet17
Under the hood135

Either side of it

v2.1.294Older

Open the release →

Names in this entry

slash/config
Open the Settings interface to adjust theme, model, output style, and other preferences. Pass one or more key=value pairs to set a setting directly without opening the interface, for example /config thinking=false, /config theme=dark, or /config model=sonnet. The key=value form also works in non-interactive mode (-p) and from the Claude mobile app via Remote Control. The key=value form can't turn on a setting that needs your confirmation in the panel, such as autoContinueAtUsageLimit, though it can turn one off. Run /config --help to list the keys it accepts. Alias: /settings
settingautoUpdatesChannel
Follow the stable release channel instead of latest

Anthropic's notes

Upstream's own release notes for v2.1.295 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.

Fixed PushNotification saying a push was not sent in claude remote-control sessions right after a phone message, without the /config toggle, or when started from inside Claude Code
Fixed changing the auto-update channel in /config saving before a plugin's config.set hook was asked

GitHub issues this fixes

A model matched these issues to Anthropic's notes, so a link can be wrong.

Is this right?