{"version":"2.1.232","anchor":"managed-policy-can-now-ship-a-fixed-settings-payload-not-jus","canonical_anchor":"managed-policy-can-now-ship-a-fixed-settings-payload-not-jus","heading":"Managed policy can now ship a fixed settings payload, not just a helper program","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/managed-policy-can-now-ship-a-fixed-settings-payload-not-jus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Managed policy can now ship a fixed settings payload, not just a helper program\n\nAdmins can ship managed settings directly in policy, including per-OS defaults, without running a helper program.\n\n**What**\n\n`policyHelpers`, the top-level setting where an IT admin points Claude Code at a program that supplies managed settings, now also accepts a plain `default` settings payload and a per-OS `defaultSettings` payload used when no helper runs or the helper cannot be reached.\n\n**Details**\n\n- `default` sits at the top of the `policyHelpers` map; `defaultSettings` sits inside each per-OS entry next to that OS's helper executable.\n- The parse-failure message for `policyHelpers` was rewritten to describe the new shape.\n- When the setting comes from an OS-admin policy source and does not parse, startup fails rather than falling back.\n\n**Evidence**\n\n`plus an optional \"default\" settings payload`\n\n- Area: Managed Settings\n- Names: `policyHelpers`, `defaultSettings`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}