codex-workflow

# Codex Workflow Deterministic multi-agent orchestration in Codex - the analog of Claude Code's Workflow tool. Pick the right level for the job. ## Three levels (cheapest first) | Need | Use | Determinism | |---|---|---| | Ad-hoc "spawn one agent per X, summarize" in a chat | **native NL spawn** | low (model decides) | | Fixed fan-out over a worklist (one worker per row, schema'd) | **`spawn_agents_on_csv`** | medium | | Collision-free parallel *implementation* | **`worktree + codex exec &`** | high (isolated) | | Scripted multi-step pipeline with structured output you parse | **`run_workflow`** (the orchestrator MCP) | high | Reach for `run_workflow` when you'd otherwise hand-wire `codex exec` calls; reach for the native paths for quick in-session work. ## `run_workflow` - the orchestrator Installed as the `codex-workflow` MCP extension (`vd mcp install codex-workflow`). Call the `run_workflow` tool with a spec: ```jsonc { "steps": [ { "id": "scan", "prompt": "List changed files vs main.", "output_schema": {"type":"object","properties":{"files":{"type":"array"}}} }, { "id": "review", "prompt": "Review {file} for bugs.", "agent": "code-reviewer", "parallel_group": "g1" } ] } ``` - **v1 shape:** sequential steps + one `parallel_group` + per-step `output_schema`. NOT loops/conditionals (those are a later iteration - script them outside, or use multiple `run_workflow` calls). - `agent` (optional) names a `~/.codex/agents/*.toml` role; its `developer_instruc...