Перейти к содержимому

Claude Code managed policy

Это содержимое пока не доступно на вашем языке.

claude-policy is the managed-policy authoring module. It is selected by default on a fresh installation and requires governance. Its descriptor is olivares.claude-policy, with API routes under /v1/m/claude-policy/.

It validates and previews one surface per managed file, in every edition:

Tool Surfaces
Claude Code managed-settings, hooks, managed-mcp, sandbox
Codex codex-requirements, codex-managed-config
Grok Build grok-requirements
OpenCode opencode-config
Gemini CLI gemini-cli-settings

Validation and dry-run do not change host configuration.

Fleet-wide management is Business: publishing an immutable policy revision and its revision history, the signed artifact that workstations pull and verify, the attested check-in and the distribution view that compares published policy with observed host configuration. Drift names the key that differs, not its value (a Codex allowlist finding also names the entries the host adds). A host whose file is absent, empty or invalid is reported as ungoverned. Publishing reports distribution status; it does not directly write host files. Missing observations do not mean that hosts comply. A Community server answers these routes with 501 and an error that names Business.

A workstation applies a surface with olivares claude-policy pull. It checks the artifact against the signing key fingerprint that publish printed, which you hand to the host out of band, then writes the file and checks in with what it reads back from disk. An artifact that does not verify exits 7 and leaves the file as it was.

Reading, validation and dry-run require governance:claude-policy:read; check-in requires governance:claude-policy:write and also read, because it answers whether the host’s file equals the published policy; publishing requires governance:claude-policy:admin. Invalid policy and inline credentials are rejected.

Use Edition & modules in the console, or the CLI:

Terminal window
olivares modules ls
olivares modules on claude-policy
olivares claude-policy validate managed-settings --content-file settings.json
olivares modules off claude-policy

See the CLI reference and Claude Code hooks as a PEP for related commands and enforcement setup.