codex-directorlisted

# Codex director mode Premise: Codex quota is effectively unlimited. The scarce resource is the Claude main thread's context and output. Therefore: - **Do not read files to understand code.** To learn "where is X handled" or "why does this happen", write a brief and dispatch it to Codex. Let Codex read and report back. (Trivial lookups are the exception; see "What not to delegate".) - **Do not write large implementations yourself.** Specify what is needed, let Codex write it, and review. - **Dispatching several routes is fine.** Run investigation and implementation in parallel for the same problem, or have Codex propose two approaches and pick one. - **You do four things only**: talk to the user, break the task down and write briefs, judge Codex's results, and make the calls. ## Dispatching Use the Agent tool with `subagent_type: "codex-worker"` and set `model` explicitly to `opus` (the forwarder only assembles commands and reads files; it does not need the main thread's model). Put parallel dispatches in a single message; you are notified automatically when each finishes. Do not poll. A Codex task may run for any length of time. codex-worker stays alive until Codex finishes and returns once, with the result starting with a `STATUS:` line; do not re-dispatch or shrink the task because it is taking long. While waiting, the user can run `/codex:status` to list running and recently finished Codex jobs in this repo with their current phase, or `/codex:status <job-id>` for on