Clodex Workflow
Prefer native Clodex coordination when the repository has been initialized with
clodex init: use the available MCP handoff tools first, and use
clodex task ..., clodex audit --diff, and clodex status as fallbacks. The
older harness commands remain valid for scripted or non-MCP workflows.
Harness commands:
clodex plan "<task>"asks Claude Code CLI to produce a structured plan.clodex build "<task>"runs Claude planning, Codex implementation, and multi-reviewer audit in an isolated worktree.clodex apply <run-id>applies an approved worktree patch back to the source checkout.clodex task start/get/cancel/listmanages durable async runs.clodex audit --diffaudits the current uncommitted diff with both Claude and Codex.clodex statusshows recent local task and run state.
Defaults:
- Claude planner/auditor:
claude -p --model opus --effort max --permission-mode plan. - Codex engineer/auditor:
codex execorcodex reviewwithgpt-5.5andmodel_reasoning_effort="xhigh". - Builds default to
.clodex/workspaces/<run-id>/; use--workspace localonly when in-place changes are intentional. - Approval profiles are
ci,local, andauto_review;ciis the deterministic default. - Subscription CLI auth is preferred. API keys are fallback-only for CI/headless use.
Do not mark a run complete unless .clodex/runs/<run-id>/05-agreement.json
contains approved: true.