{"version":"2.1.228","anchor":"new-policyhelpers-managed-settings-key-for-per-os-policy-hel","canonical_anchor":"new-policyhelpers-managed-settings-key-for-per-os-policy-hel","heading":"New policyHelpers managed-settings key for per-OS policy helper executables","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/new-policyhelpers-managed-settings-key-for-per-os-policy-hel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### New `policyHelpers` managed-settings key for per-OS policy helper executables\n\nSet policyHelpers per platform; WSL falls back to the linux entry, then to the single policyHelper.\n\n**What**\n\nAdministrators can now set a different policy helper executable per platform. `policyHelpers` is an object keyed by `macos`, `linux`, `windows` and `wsl`; the entry matching the current platform wins over the existing single `policyHelper`, and a platform with no entry falls back to `policyHelper`. A `wsl` machine with no `wsl` entry tries the `linux` entry first.\n\n**Details**\n\n- Like `policyHelper`, `policyHelpers` is honored only when it arrives from an admin-controlled policy source, not from user or project settings.\n- Validation is strict: a malformed `policyHelpers` from an OS-admin policy source is fatal at startup.\n- If `policyHelpers` is configured but has no entry for the current platform and no `policyHelper` is set, a warning is logged and no helper runs.\n\n**Evidence**\n\n`Per-OS variant of policyHelper, keyed by platform: macos, linux, windows, wsl.`\n\n- Area: Managed Settings\n- Names: `policyHelpers`, `policyHelper`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}