Skip to main content
The harness enforces model allowlists based on compliance requirements. When a compliance mode is set, only models in the corresponding allowlist are permitted.

Compliance Modes

Usage

Or as agent metadata:

Enforcement Behavior

When a model outside the allowlist is requested:
  • In observe mode: the trace records action: "switch_model" with the suggested compliant alternative, but execution continues with the original model
  • In enforce mode: the harness blocks the non-compliant model and either switches to a compliant alternative or stops execution

Combining with Budget

Compliance and budget constraints are independent. Both are checked at every step:

Custom Allowlists

The built-in allowlists cover common regulations. For custom requirements, set compliance at the integration level or use the HarnessConfig directly: