Invoke Harness

Run the selected harness as a bounded child process. Read only its reference:

• Codex
• Claude Code
• Grok
• OpenCode
• Cursor CLI
• GitHub Copilot CLI
• Cockpit

Procedure

1. Resolve the documented executable with command -v and its real path, then verify product identity, version, and required flags with current --version and --help output. Abort on an identity or required-flag mismatch. Local help may override flag names, but not the reference's noninteractive agent command unless the user requested another product feature. Record the resolved executable path, its SHA256 content digest, version, and relevant account/config identity without printing secrets. If it is a wrapper, also identify the underlying installation. Reuse verified setup facts within one run only while the executable, underlying installation, version, and relevant account/config identity remain verifiably unchanged; otherwise rerun verification. Invalidate on invocation or verification failure. Never cache worker output, review results, or permissions.
2. Use the harness's noninteractive mode. Set the model and working directory explicitly for each task. Resolve nicknames to actual CLI model IDs and confirm through the reference's model-list command when available; otherwise use its fallback and report the ID as unverified. Reuse current-run model discovery only while the binary, version, and relevant account/config identity remain unchanged. Start a fresh child process and session for every task unless the user requests continuation.
3. Pass short prompts as one quoted argument. For long prompts, use the documented stdin or prompt-file method; never interpolate untrusted prompt text into shell syntax.
4. Confirm the requested working directory, environment, and operations are within the user's authorized scope and compatible with applicable restrictions before launch. If they are not, do not launch; report the conflict or missing authorization. External harness invocations run without a harness sandbox and with all permissions bypassed. Use the exact no-sandbox/all-permissions settings in the selected reference. Abort if the installed harness cannot satisfy this policy.
5. Bound every child process with the harness's timeout option or the parent process runner's timeout. Capture stdout, stderr, and the exit status. Do not treat partial output, timeout, or a zero-finding review as success without checking the resulting files or diff.