ask-codexlisted

# Ask Codex a question For a single question with a single answer. Anything multi-step or long-running belongs to a subagent (`codex-second-opinion`, `codex-reviewer`, `codex-debugger`). ```bash codex-run -C <repo-dir> "<self-contained question>" ``` `codex-run` prints **only Codex's final answer** on stdout (it captures the final message via `codex exec -o` rather than dumping the whole event log). It defaults to a read-only sandbox, so Codex can read the repo but cannot change anything. ## Writing the question Codex has zero knowledge of this conversation. Every question must stand alone: - Name the files or directories it should look at. - State what you already know or already tried. - Say what shape of answer you want ("name the single most likely cause and the line to look at", "answer yes/no then justify in three sentences"). ```bash codex-run -C /path/to/repo \ "In src/auth/session.ts, refreshToken() occasionally returns a token that fails validation immediately. I suspect a clock-skew issue in the exp comparison. Read that file plus src/auth/jwt.ts and tell me the single most likely root cause and the exact line. Be concise." ``` ## Useful options ``` -s workspace-write let Codex modify files (only when the user asked for that) -m gpt-5-codex model override -r continue the previous codex session (follow-up question) --timeout 1800 raise the 900s default for a big repo sweep --raw also print Codex's full even