tine harnesses

List the command each harness runs, whether its executable is on PATH, and its model, usage, cost, and tool capture fidelity. There are 25 choices, including the operator-configured generic harness.

tine harnesses
tine harnesses --installed
tine harnesses --json

tine run --harness codex --prompt "Inspect this repo" --save codex.tine
tine price codex.tine --json

Harness choices

claude-code, codex, gemini, qwen-code, cursor, opencode, pi, hermes, openclaw, kimi-code, grok, goose, amp, droid, copilot, auggie, cline, qoder, continue, openhands, vibe, aider, crush, kiro, generic.

Read fidelity before relying on a field

yes means the parser records that field; no means it does not. flag means model identity depends on an explicit model flag. unverified identifies a documented JSON mode whose event schema has not been verified. An installed executable alone does not establish its capture fidelity.

Codex uses exec --json by default and records per-turn usage differences, model resolution, and tool activity. Other presets use documented JSON modes where available. Cost is recorded only when the CLI reports a dollar amount; Copilot premium-request multipliers remain a separate attribute. The JSON catalog exposes one object with command and harnesses.

Output trust

The last output-format option determines JSON capture. Text-mode stdout and all stderr remain text. A malformed event is retained as text, and malformed metering fields produce a warning instead of aborting the run. Only an operator-written generic command supports free-text cost parsing.

Use --harness-command to replace a preset invocation and --harness-arg to add arguments. Pi now has its own default command. See tine run for process bounds, autosave, and environment controls.