> ## Documentation Index
> Fetch the complete documentation index at: https://agent-compass.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Understand the ownership, workflow, and completion criteria for an AgentCompass harness integration.

A harness adapts an agent framework, CLI, or direct model-call workflow to the AgentCompass runtime. It receives a
`PreparedTask` and an `EnvironmentSession`, owns the execution loop, and returns a normalized `RunResult` for benchmark
evaluation.

## Integration Boundary

The harness owns agent setup, prompt and workspace handoff, model interaction, tool execution, trajectory capture,
usage, completion state, and harness cleanup. It must not load benchmark datasets, interpret benchmark correctness,
select provider-specific task images, or create its own untracked sandbox lifecycle.

## Integration Workflow

1. [Implement the harness contract](/en/developer_guide/harness_integration/code_implementation), including compatibility,
   session lifecycle, installation, limits, secrets, and result normalization.
2. [Update public documentation](/en/developer_guide/harness_integration/documentation_update) with supported protocols,
   environments, parameters, and complete commands.
3. [Validate the integration](/en/developer_guide/harness_integration/validation_and_alignment) across real tasks, protocols,
   environments, failure paths, concurrency, and any official alignment claim.

## Completion Gate

* Compatibility follows capabilities and fails before expensive work.
* Setup, run, and cleanup phases have explicit behavior.
* Every claimed protocol, environment, and installation strategy has real evidence.
* Results preserve answer, trajectory, usage, limits, termination, and error meaning.
* Secrets are redacted from every persisted and displayed surface.
* Public documentation matches the implemented schema and runnable combinations.