Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Managed settings: policy helpers can carry a static fallback payload

Use it now
Useful3 Signal3
Managed Settings Notable

Admins can attach a static defaultSettings payload used when a policy helper is missing or fails.

policyHelpersdefaultSettingsdefault
What

Admin policy sources can now put a defaultSettings payload on each per-OS entry of policyHelpers (or under a top-level default key). If no helper is configured for the platform, or the helper fails at startup or on a refresh, that payload is applied with no process spawned instead of the previous retain-or-fail behaviour.

Details
  • Failures are logged as "applying the static ... settings payload" and counted in the settings_policy_helpers_per_os telemetry as fell_back_to_default_on_failure or refresh_fell_back_to_default.
  • A payload that does not parse is reported as default_payload_invalid and refuses startup.
  • If a helper later recovers on a refresh tick, its output replaces the static default.
  • Putting defaultSettings on the singular policyHelper key is ignored and produces a status warning saying static fallback payloads belong on the per-OS policyHelpers entries.
Evidence

fell_back_to_default_on_failure, policyHelper refresh: helper recovered; its output replaces the static default settings payload

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.232 →