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

appendPlugins

setting gone documented JSON

A Claude Code settings key, read out of the shipped bundle. It was in the build from v2.1.268 and was gone by v2.1.284.

Run your organization's mods after every mod a user installs

Anthropic's own wording. Read off All settings, captured 2026-11-06.

First seen v2.1.268 10 Sep 2026
Last seen v2.1.283 25 Sep 2026, gone by v2.1.284
Builds15 / 159on this box, as of v2.1.319
Written about v2.1.259 first named in a changelog, 2 Sep 2026
v2.1.268in the build not in the build never minedv2.1.319

In the changelogs

9

Releases whose published page names appendPlugins.

  1. v2.1.311
    Organizations can pin plugin hook code to known fingerprints

    Managed settings can now list fingerprints of approved plugin releases, and a hooks plugin loads only from a folder that matches one

    found in this entry's text

  2. v2.1.311
    Remote plugins can now get organization-level status

    A remote plugin now gets organization-level status when managed settings name its digests under pluginDigests and list it in prependPlugins or appendPlugins

    found in this entry's text

  3. v2.1.295
    New check on plugin settings loaded from machine-level files

    Claude Code now checks plugin-related settings that come from settings files users cannot write to

    found in this entry's text

  4. v2.1.292
    Reworked handling of organization plugin ordering, and stricter search errors

    How prependPlugins and appendPlugins are worked out has changed, and file search can now stop with an error when it cannot read its input

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

  5. v2.1.268
    Managed plugins can pin hook ordering with prependPlugins/appendPlugins

    Org admins can now pin specific plugins to run first or last among hooks

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

  6. v2.1.267
    User-writable settings files can no longer set secDefault/prependPlugins/appendPlugins or enable plugins via enabledPlugins

    User-writable settings files can no longer set secDefault, prependPlugins, appendPlugins, or enable plugins

    found in this entry's text

  7. v2.1.267
    Managed-policy plugin seating warnings for prepend/append conflicts

    New warnings flag when a managed plugin's ordering or a settings key gets silently overridden by managed policy

    found in this entry's text

  8. v2.1.267
    New prependPlugins/appendPlugins managed-settings keys

    prependPlugins and appendPlugins now fall back to an empty list on malformed values

    found in this entry's text

  9. v2.1.259
    Managed plugin ordering conflict warning

    A managed plugin listed in both prepend and append lists now warns about the conflict and is prepended.

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

First cited

3

The earliest release whose published evidence quoted appendPlugins was v2.1.259, 2 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.2592 Sep 2026is named in both prependPlugins and appendPlugins; it is prepended
v2.1.2679 Sep 2026managed plugin ${p} is named in both prependPlugins and appendPlugins; it is prepended
v2.1.31126 Oct 2026A plugin delivered from a remote source takes the tier when managed settings name its digests under pluginDigests on that marketplace and list it in prependPlugins or appendPlugins.

Presence across releases

2
BuildsHow manyDatesReading
v2.1.268 – v2.1.28315 builds10 Sep 2026 → 25 Sep 2026 ◆in the build
v2.1.284 – v2.1.31933 builds28 Sep 2026 → 6 Nov 2026 ○not in the build

Build by build

48

One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.

BuildDateStateThe record behind it
v2.1.26810 Sep 2026·addedverdict: added
v2.1.26911 Sep 2026·presentverdict: present
v2.1.27012 Sep 2026·presentverdict: present
v2.1.27114 Sep 2026·presentverdict: present
v2.1.27214 Sep 2026·presentverdict: present
v2.1.27315 Sep 2026·presentverdict: present
v2.1.27416 Sep 2026·presentverdict: present
v2.1.27517 Sep 2026·presentverdict: present
v2.1.27618 Sep 2026·presentverdict: present
v2.1.27718 Sep 2026·presentverdict: present
v2.1.27819 Sep 2026·presentverdict: present
v2.1.28022 Sep 2026·presentverdict: present
v2.1.28123 Sep 2026·presentverdict: present
v2.1.28224 Sep 2026·presentverdict: present
v2.1.28325 Sep 2026·presentverdict: present
v2.1.28428 Sep 2026·removedverdict: removed
v2.1.28529 Sep 2026·absent—
v2.1.28630 Sep 2026·absent—
v2.1.2871 Oct 2026·absent—
v2.1.2882 Oct 2026·absent—
v2.1.2893 Oct 2026·absent—
v2.1.2905 Oct 2026·absent—
v2.1.2916 Oct 2026·absent—
v2.1.2926 Oct 2026·absent—
v2.1.2937 Oct 2026·absent—
v2.1.2948 Oct 2026·absent—
v2.1.2958 Oct 2026·absent—
v2.1.2969 Oct 2026·absent—
v2.1.29914 Oct 2026·absent—
v2.1.30014 Oct 2026·absent—
v2.1.30115 Oct 2026·absent—
v2.1.30216 Oct 2026·absent—
v2.1.30318 Oct 2026·absent—
v2.1.30419 Oct 2026·absent—
v2.1.30520 Oct 2026·absent—
v2.1.30621 Oct 2026·absent—
v2.1.30721 Oct 2026·absent—
v2.1.30822 Oct 2026·absent—
v2.1.30922 Oct 2026·absent—
v2.1.31023 Oct 2026·absent—
v2.1.31126 Oct 2026·absent—
v2.1.31227 Oct 2026·absent—
v2.1.31430 Oct 2026·absent—
v2.1.31530 Oct 2026·absent—
v2.1.31631 Oct 2026·absent—
v2.1.3172 Nov 2026·absent—
v2.1.3183 Nov 2026·absent—
v2.1.3196 Nov 2026·absent—

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