Skip to main content

Module harness

Module harness 

Source
Expand description

The harness adapter API — the single seam between generic run-mode code and harness-specific behavior.

Every harness-specific concern hangs off the HarnessAdapter trait: how discoverable skills are presented in a dispatch prompt, how a persisted transcript is parsed, where staged skills live, and which native hook the write guard installs. Generic code resolves an adapter with adapter_for and then calls the trait — so adapter_for is the one place that names a concrete harness for this surface.

Structs§

ClaudeCodeAdapter
CliDispatchContext
Context for rendering a harness’s one-shot CLI agent-dispatch guidance.
CliJudgeContext
Context for rendering a harness’s one-shot CLI judge-dispatch guidance.
CliManifestContext
Context for rendering a harness’s dispatch-manifest.md CLI recipe.
CodexAdapter
OpenCodeAdapter

Constants§

HEADLESS_RUNBOOK_TEMPLATE
The shared headless (human-followed) RUNBOOK.md template used by every Cli-dispatch run, regardless of harness (Codex, OpenCode, and Claude Code in hybrid/headless).

Traits§

HarnessAdapter
The behavior that varies by harness. Generic run-mode code depends on this trait, never on a concrete harness variant.

Functions§

adapter_for
Resolve the adapter for a Harness. This is the single dispatch point on the harness variant for all harness-specific behavior; every other module goes through the returned trait object.