{"version":"2.1.296","anchor":"managed-policies-accept-a-code-key-as-alternative-to-cli","canonical_anchor":"managed-policies-accept-a-code-key-as-alternative-to-cli","heading":"Managed policy entries can carry a code section as well as cli","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/managed-policies-accept-a-code-key-as-alternative-to-cli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Managed policy entries can carry a `code` section as well as `cli`\n\nEntries in `managed.policies` now accept a `code` key in addition to `cli`, and validation messages point to whichever one the entry uses\n\n**Unclear.** Which settings belong under `code` rather than `cli` is not stated.\n\n**What**\n\nManaged policies are settings an organization's administrator sets centrally for Claude Code. Each entry in the `managed.policies` list could already hold a `cli` section. Claude Code now also accepts a `code` key in an entry.\n\nWhen Claude Code checks a policy entry and reports a problem, the location it names now ends in `code` for entries that use that section, and in `cli` otherwise.\n\n**Why**\n\nAdministrators writing managed policies now have a second section name available, and a policy that uses `code` is no longer rejected as an unknown key. The policy format is growing a section specific to `code`.\n\n- Area: Managed Settings\n- Names: `managed.policies`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}