Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

settings.read

setting never mined JSON

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

Plugins and hooks gain new permission scopes: session.usage, settings.read, env.get, env.set

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.267.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 159on this box, as of v2.1.319
Written about v2.1.267 first named in a changelog, 9 Sep 2026

In the changelogs

7

Releases whose published page names settings.read.

  1. v2.1.304
    Plugin modules can now see and override settings through a settings.read event

    Plugin modules can subscribe to a settings.read event that shows them the settings in effect and lets them override values

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

  2. v2.1.304
    Plugins can intercept queued messages, and session.send checks the input hold

    Hook plugins can now intercept a queued message, and a plugin's session.send is refused if Claude Code cannot read whether plugin input is held

    found in this entry's text

  3. v2.1.304
    Settings supplied by hook plugins are re-read when settings or plugins change

    Claude Code now re-reads settings supplied by settings.read hooks whenever your settings or loaded plugins change

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

  4. v2.1.280
    Builtin hooks-module capability manifests expanded

    Builtin plugin hook modules were granted access to more host calls, including two new environment variables

    found in this entry's text

  5. v2.1.267
    New plugin/hook capability scopes: session.usage, settings.read, env.get, env.set

    Plugins and hooks gain new permission scopes: session.usage, settings.read, env.get, env.set

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

  6. v2.1.267
    Plugin API gains fs.read/write/list rename plus new settings.read, env.get, env.set

    Claude Code's plugin API renames its file actions and adds settings.read, env.get and env.set

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

  7. v2.1.267
    Plugin/hook capability namespace gains session and env access

    Hooks and plugins can now access session usage stats and read/write environment variables

    found in this entry's text

First cited

4

The earliest release whose published evidence quoted settings.read was v2.1.267, 9 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.2679 Sep 2026"settings.read", "env.get", "env.set",
v2.1.2679 Sep 2026"settings.read": { check: (n) => ics(n?.source), run: (n) => scs(n) }
v2.1.30419 Oct 2026never settles under a settings.read hook
v2.1.30419 Oct 2026settings.read: refused to the engine

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 settings key does. All settings keys.

Feedback