Codex's managed requirements

An organization can deploy managed requirements for Codex on your Mac: rules that limit the settings Codex may run with. HarmFlow runs Codex tasks unattended, with settings of its own: the approval policy never, and the sandbox mode the task's permission profile maps to. When the requirements do not allow one of those settings, HarmFlow warns you, in the AI tools list and on the executions it concerns. Neither warning stops a task: Codex's tasks still start and run.

The warning in the AI tools list

HarmFlow asks Codex for its managed requirements when it checks it. When they do not allow a setting HarmFlow runs Codex with, Codex still reads Ready in the AI tools list, but in a warning tone rather than as a plain ready tool, with a diagnostic that says why. The diagnostic shows when you hover over Codex's status in the AI tools list, and in the Diagnostic row of Codex in the AI tools section of Settings, where the Managed requirements row reads "Managed by an administrator" and lists what the requirements allow.

The diagnostic names each setting the requirements do not allow, and what they allow instead. For requirements that allow only the approval policies on-request and untrusted, it reads: "Codex's managed requirements do not allow approval_policy = never, which HarmFlow runs it with, so Codex falls back to what they allow: approval_policy = on-request, untrusted"

When the requirements do not allow a sandbox mode a permission profile maps to, the diagnostic names sandbox_mode the same way; when they disallow both settings, it names both.

The warning does not keep Codex from running: tasks that use Codex still start, as they would with no requirements.

When HarmFlow cannot read the requirements, it does not guess: Codex shows no warning tone and no diagnostic about them, as it would with none.

The warning on an execution

As a task starts, Codex may report that its requirements override one of the settings HarmFlow gave it, and that it falls back to a value they allow. The execution goes on, and carries a warning that quotes Codex's own notice, which begins, for the approval policy: "Configured value for `approval_policy` is disallowed by requirements; falling back to required value OnRequest."

The warning is in two places:

• The Results view. Its Warnings list shows it, marked Warning and followed by Codex's notice.
• The Events view. The execution's log holds it as a warning event, with the same notice.

Only what needs the setting Codex did not take is affected: a command that the allowed value holds back may not run as the task expects. The notice tells you which setting changed, and the requirements your organization manages say what Codex allows.