Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Settings keys

managedSettings

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.

Remote-delivered managed settings now reject risky helper paths and inline scripts, and strip claudeMd

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

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 162on this box, as of v2.1.323
Written about v0.2.85 first named in a changelog, 25 Apr 2025

In the changelogs

7

Releases whose published page names managedSettings.

  1. v2.1.323
    Apps built on Claude Code can pass managed settings when they start it

    Apps that embed Claude Code through its SDK can now pass managed settings when the session starts, along with plugins

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

  2. v2.1.281
    SDK/CLI --managed-settings payload is now loaded at startup alongside --settings

    The --managed-settings payload, including the SDK's managedSettings option, is now actually loaded at startup

    found in this entry's text

  3. v2.1.257
    managedSettings 'merge' mode composition rules made explicit and expanded

    Managed settings merge mode now documents which fields the helper replaces wholesale rather than merging.

    found in this entry's text

  4. v2.1.242
    Policy helper output can merge into a source's settings instead of replacing it

    Policy helper output can merge into a source's settings, so a failure costs less.

    found in this entry's text

  5. v2.1.235
    Remote-delivered managed settings get stricter path and payload rules

    Remote-delivered managed settings now reject risky helper paths and inline scripts, and strip claudeMd

    found in this entry's text

  6. v2.1.136
    Enterprise Managed Settings Helper

    found in this entry's text

  7. v0.2.85
    New Features

    found in this entry's text

First cited

5

The earliest release whose published evidence quoted managedSettings was v2.1.242, 24 Aug 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.24224 Aug 2026"How the helper's managedSettings compose with the settings of the source that delivered this entry: 'replace' (default) - the output is the policy; 'merge' - the output is deep-merged over that source's own settings (helper keys win, arrays replace), so a failed helper costs only the delta"
v2.1.28123 Sep 2026...(t.managedSettings ? ["--managed-settings", t.managedSettings] : []),
v2.1.28123 Sep 2026managedSettings: vD("--managed-settings")
v2.1.28123 Sep 2026managedSettings: void 0
v2.1.32312 Nov 2026managedSettings

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