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
Home / Reference / Settings keys

managed.policies

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.

Gateway operators get startup errors for bad desktop policy keys instead of silently passing them through.

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

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.232 first named in a changelog, 13 Aug 2026

In the changelogs

5

Releases whose published page names managed.policies.

  1. v2.1.296
    Managed policy entries can carry a code section as well as cli

    Entries in managed.policies now accept a code key in addition to cli, and validation messages point to whichever one the entry uses

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

  2. v2.1.283
    Models denied in the catch-all managed policy now apply to every policy

    deniedModels in the catch-all managed.policies entry is now combined with each specific policy's list instead of being replaced by it

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

  3. v2.1.281
    Self-hosted gateway: Bedrock guardrail and assume_role, telemetry resource_attributes, serve_to_desktop

    The self-hosted gateway config adds Bedrock guardrails and assume_role, telemetry resource_attributes, and serve_to_desktop for policies

    found in this entry's text

  4. v2.1.232
    Gateway desktop: policy overlays are validated before serving

    Gateway operators get startup errors for bad desktop policy keys instead of silently passing them through.

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

  5. v2.1.232
    Managed policy CLI documents are checked for alias collisions

    Gateway configs now fail validation if a setting appears under both an alias and its canonical name.

    found in this entry's text

First cited

1

The earliest release whose published evidence quoted managed.policies was v2.1.296, 9 Oct 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.2969 Oct 2026managed.policies[${h}].${f.underCode ? "code" : "cli"}

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