policyHelpers
A Claude Code settings key, read out of the shipped bundle. It has been in the build since v2.1.228, including the newest one read.
What it is
An admin policy helper can no longer chain to another policy helper.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.228.
Presence across releases
| Releases | Reading | Declared type | Default |
|---|---|---|---|
| 2.1.245 – 2.1.251 6 releases | never mined | — | — |
| 2.1.228 – 2.1.243 15 releases | in the build | — | — |
A row reading never mined is a release with no archived bundle behind it. Nothing was read out of it, so nothing here says whether the name was in it. A declared type or a default is only ever what that release's own bundle stated.
Changelog entries naming it
-
v2.1.242Policy helpers can declare whether their settings merge or replace
Admins can say whether a per-OS policy helper's settings replace or merge over the source.
named in this entry
-
v2.1.239Policy-helper warnings say which platform they apply to
policyHelpers warnings now understand per-OS entries and say when yours has none.
named in this entry
-
v2.1.235Policy helpers can be delivered by remote managed settings, after explicit approval
Org policy helpers can now arrive via remote settings, but only run after an admin approves the exact payload.
named in this entry
-
v2.1.234Managed policy helpers can be an inline script instead of an executable
Admins can now supply managed policy helpers as an inline script instead of a file on disk.
named in this entry
-
v2.1.232Warnings when policy helper settings are nested in the wrong place
Settings validation now warns when policy helper keys are nested where nothing reads them.
named in this entry
-
v2.1.232Fixed policy payloads are validated like managed settings
Malformed admin fallback settings payloads are caught at startup instead of silently doing nothing.
named in this entry
-
v2.1.232A failing policy helper now falls back to its fixed payload
A repeatedly failing policy helper now serves its configured fixed payload instead of stale output.
named in this entry
-
v2.1.232Managed settings: policy helpers can carry a static fallback payload
Admins can attach a static
defaultSettingspayload used when a policy helper is missing or fails.named in this entry
-
v2.1.232Policy helper settings are now per-OS with a static fallback
Policy helpers now take per-OS entries plus a static settings payload used when they fail.
named in this entry
-
v2.1.232Policy helper executable paths must be in normalized form
Policy helper paths must be fully normalized, and Windows needs a drive or UNC path.
named in this entry
-
v2.1.232Managed policy can now ship a fixed settings payload, not just a helper program
Admins can ship managed settings directly in policy, including per-OS defaults, without running a helper program.
named in this entry
-
v2.1.228A policy helper can no longer configure another policy helper
An admin policy helper can no longer chain to another policy helper.
named in this entry
-
v2.1.228Managed settings accept per-OS
policyHelpersAdmins can set a different policy helper program per operating system with a new policyHelpers setting.
named in this entry
-
v2.1.228New
policyHelpersmanaged-settings key for per-OS policy helper executablesSet policyHelpers per platform; WSL falls back to the linux entry, then to the single policyHelper.
named in this entry
Documentation pages
None of Anthropic's documentation pages this site has a copy of carries this name.
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.