Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial

/settings-review

slash never mined JSON

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

Claude Code now blocks direct writes to the settings-review staging store

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

First seennever in a mined build
Last seen never in a mined build
Builds0 / 123on this box, as of v2.1.280
Written about v2.1.269 first named in a changelog, 11 Sep 2026

In the changelogs

4

Releases whose published page names /settings-review.

  1. v2.1.269
    New protection preventing direct writes to the settings-review store

    Claude Code now blocks direct writes to the settings-review staging store

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

  2. v2.1.269
    New feature: settings file writes can be staged for owner review instead of applied directly

    New settings-review system can stage settings file changes for owner approval instead of applying them immediately, though it isn't active in this build

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

  3. v2.1.269
    Edit tool result can now be 'staged for review' pending settings owner approval

    Edit tool results can now report a change as 'staged for review' instead of applied, when settings files require owner approval

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

  4. v2.1.269
    New settings-review exemption bookkeeping for plugin/skill-managed settings paths

    /settings-review now recognizes more plugin-related settings file locations for its exemption rules

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

First cited

4

The earliest release whose published evidence quoted /settings-review was v2.1.269, 11 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.26911 Sep 2026Staged Claude Code settings changes are the owner's to review in /settings-review; the review store cannot be written directly
v2.1.26911 Sep 2026Staged for review: ${e} was NOT modified. Changes to Claude Code settings files made without the owner of this computer approving them in person are held for their review; the owner applies or discards them with /settings-review
v2.1.26911 Sep 2026Staged for review: ${e} was NOT modified. Changes to Claude Code settings files made without the owner of this computer approving them in person are held for their review; the owner applies or discards them with /settings-review, and the change takes effect only if they accept it.
v2.1.26911 Sep 2026Staged for your review · not applied until you accept it in /settings-review

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 slash command does. All slash commands.

Feedback