Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

ConfigChange

hook never mined documented JSON

A Claude Code hook event, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

When a configuration file changes during a session

Anthropic's own wording. Read off Hooks reference, captured 2026-10-22.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 149on this box, as of v2.1.308
Written about v2.1.48 first named in a changelog, 19 Feb 2026

In the changelogs

6

Releases whose published page names ConfigChange.

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

    found in this entry's text, named in this entry

  2. v2.1.287
    Held settings changes can be accepted or discarded, including for cloud sessions

    Settings edits Claude made without your approval are held for you to accept, discard or leave, and cloud sessions use only accepted versions

    found in this entry's text

  3. v2.1.277
    Plugin-dir file watcher with adaptive polling and ConfigChange hook gate

    Plugin skill directories now get watched for changes, with adaptive polling and a ConfigChange hook gate

    found in this entry's text

  4. v2.1.229
    Hooks are handed a session object instead of reading globals

    Hooks now get an explicit session with id, working directory and project root instead of guessing from globals.

    found in this entry's text

  5. v2.1.48
    HTTP Hooks

    found in this entry's text

  6. v2.1.48
    ConfigChange Hook Event

    found in this entry's text

First cited

3

The earliest release whose published evidence quoted ConfigChange was v2.1.277, 18 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.27718 Sep 2026a ConfigChange hook blocked the reload, the loaded version stays
v2.1.2882 Oct 2026ConfigChange hook blocked reapplying
v2.1.30419 Oct 2026skillChangeDetector: ConfigChange hook gate not wired

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the hook event does. All hook events.

Feedback