Codex

Profiles

• (no profile), read-only analysis (no compilation, no tests)
• --profile edit, local edits, build, or test (workspace-write, full-auto)
• --profile full, network or broad filesystem access (danger-full-access, full-auto)

Use --profile edit whenever the task involves go test, go build, or any command that writes build artifacts. The default read-only sandbox blocks all writes including compiler temp dirs.

For complex tasks, add --config model_reasoning_effort="xhigh".

Model Selection

Default to the project model in .codex/config.toml (gpt-5.4).

Use --model gpt-5.3-codex-spark for speed-first interactive work:

• tight back-and-forth iteration
• quick bug fixes and targeted edits
• small-to-medium refactors or UI tweaks
• rapid prototyping where frequent redirect/interrupt is expected

Stay on default gpt-5.4 for depth-first work:

• long autonomous runs
• broad multi-file changes with heavy reasoning
• test-heavy or verification-heavy tasks
• higher correctness/risk surfaces where deeper reasoning is worth the extra latency

If the user explicitly requests a model, follow the user's request.

Commands

Project defaults in .codex/config.toml. Always include --skip-git-repo-check and 2>/dev/null. Only override model when the user explicitly requests it, or when the task clearly fits the Spark speed-first criteria above.

Use case	Command
Read-only analysis	codex exec --skip-git-repo-check -o "$CODEX_OUT" "prompt" 2>/dev/null
Speed-first interactive loop (Spark)	add --model gpt-5.3-codex-spark
Apply local edits	add --profile edit
Network / broad access	add --profile full
Resume session	echo "prompt" | codex exec --skip-git-repo-check -o "$CODEX_OUT" resume --last 2>/dev/null

Create a temp file for output before running: CODEX_OUT=$(mktemp /tmp/codex-out.XXXXXX). Read the result from $CODEX_OUT after completion.