Skip to main content
Select a registered harness and configure its complete harness-parameter schema. A harness defines how an agent attempts a prepared task. It may call a model directly, launch a coding or terminal CLI, or integrate an external agent framework. The benchmark still owns task preparation and scoring. Use the recommended harness on the selected benchmark page when reproducing an official result. Choose another harness only when its page confirms that the model protocol, environment, workspace, and prepared-task contract are compatible.

​
Find a Harness

Use the live registry to see the harnesses available in your installed AgentCompass revision:
The sidebar links to harnesses with dedicated protocol, installation, parameter, execution, and troubleshooting documentation. For any registry entry, including a newly integrated harness without a dedicated page, inspect its current configuration schema with:

​
Configure Harness Parameters

The Run Parameter Reference introduces --harness-params <json>. The <json> value contains fields owned by the selected harness:
Unlike benchmark parameters, harness parameters have no user-facing fields shared by every harness. The selected harness defines the complete schema.

​
Inspect the Complete Schema

Print every accepted field, type, default, and description from the selected harness implementation:
The harness page explains valid values, supported protocols and environments, installation behavior, and interactions that cannot be expressed by type and default alone.

​
Build the JSON Object

For example, mini_swe_agent exposes executable, version, installation, step, cost, timeout, environment, and artifact settings in one object:
This expanded object demonstrates the schema; it is not a recommendation to repeat defaults. Pass only the fields that must differ from the effective harness configuration. --harness-params must be valid JSON. CLI values deep-merge over matching fields under the Harness ID in the configuration file’s harnesses section. Inspect the merged built-in and configuration-file values before adding the final CLI override:

​
Keep Parameter Ownership Clear

Agent turn limits and installation settings belong in --harness-params. Dataset filters and verifier behavior belong in --benchmark-params; model inference requests belong in --model-params; sandbox images, resources, and network policies belong in --env-params. Set the entire agent execution budget with run_timeout_seconds under execution. The selected Harness defines limits for individual tool commands or model requests, passed through --harness-params or --model-params. See Request and Command Limits for examples and links to component parameters.