Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.287 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

The path for reapplying settings changes after a ConfigChange hook was removed

Claude Code no longer has its separate step that ran ConfigChange hooks and then reloaded a changed settings file

You'll notice Removed
JSON All of v2.1.288
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
HooksArea: what it touches
RemovedKind: in v2.1.288,
RemovedSection of the release
What

Claude Code had a separate step for reapplying a changed settings file. It first ran your ConfigChange hooks, and if none of them blocked it, it reloaded the settings. A hook is a command you set up for Claude Code to run automatically at certain moments, and ConfigChange hooks run when a configuration file changes during a session. That reapply step has been removed. So has the message saying a ConfigChange hook blocked reapplying.

Why

If you use ConfigChange hooks to vet settings reloads, they may no longer be asked before a changed settings file is reapplied this way.

Read from
Names in the bundleConfigChange
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether another path now does this reapplying.

See this entry in the whole of v2.1.288 →

Feedback