codex-exec

# Codex Exec — one-shot runtime adapter Run exactly one caller-supplied Codex prompt and capture its result. This skill does not choose work, retry failures, validate by itself, or control continuation. One prompt, one process, one captured artifact is what makes the run auditable: when nothing loops, every byte of output traces to exactly one invocation, and a disagreement about what happened is settled by the artifact. Named failure mode — **stdin hang**: a non-TTY run left waiting forever on an open stdin nobody will write to; always pipe the prompt or close the stream. Anti-pattern: granting workspace-write or network access "in case the prompt needs it". Corrective: match the sandbox to the declared effects; a review prompt runs read-only, full stop. ## Procedure 1. Confirm the intended executable, profile, and caller-supplied prompt. 2. Set the working root explicitly with `-C`. 3. Match the sandbox to the requested effects: read-only for offline review, workspace-write for authorized edits, and broader access only when the caller explicitly requires network or external effects. 4. Use `scripts/lib/codex-exec.sh` and `codex_exec_guarded`. Pipe the prompt, provide a prompt file/argument, or close stdin in non-TTY execution. 5. Supply `CODEX_EXEC_TIMEOUT` as positive finite seconds or inherit an absolute `CODEX_EXEC_DEADLINE_EPOCH`. There is no fixed ten-minute default: without an explicit timeout, use the deadline's remaining time; with both, the ...