codex

# Codex Skill Guide ## Running a Task 1. Ask the user (via `AskUserQuestion`) which model to run (`gpt-5.2-codex` or `gpt-5.2`) AND which reasoning effort to use (`xhigh`, `high`, `medium`, or `low`) in a **single prompt with two questions**. 2. Select the sandbox mode required for the task; default to `--sandbox read-only` unless edits or network access are necessary. 3. Run `codex --version` first. Stop and report the failure if Codex is unavailable. 4. Assemble the command with the appropriate options: - `-m, --model <MODEL>` - `--config model_reasoning_effort="<xhigh|high|medium|low>"` - `--sandbox <read-only|workspace-write|danger-full-access>`; some Codex CLI versions also support `workspace-read-network-write` - `-C, --cd <DIR>` - `--add-dir <DIR>` - `--skip-git-repo-check` - `--dangerously-bypass-approvals-and-sandbox` 5. Do not use `--skip-git-repo-check` by default. Use it only when the user explicitly asks to run outside a Git repository or has approved that boundary bypass for this command. 6. When continuing a previous session, use `codex exec resume --last` via stdin. Do not add model, reasoning, or sandbox flags on resume unless the user explicitly requests an override. 7. **IMPORTANT**: By default, append `2>/dev/null` to `codex exec` commands to suppress thinking tokens (stderr). Only show stderr if the user explicitly requests it or if debugging is needed. 8. Run the command, capture stdout/stderr (filtered as appropriate), and summariz...