OMX
Oh My CodeXv0.18.9

Configuration

Reference for `.codex/config.toml`, `.codex/hooks.json`, and CLI flags

OMX reads configuration from ~/.codex/ (user-level) and .codex/ (project-level). When the same key appears in both, the project-level value takes precedence.

.codex/config.toml

FieldTypeDescription
modelstringDefault model (e.g. "gpt-4.1", "o3")
codex_hooksboolEnable the OMX hook pipeline. Set to true to activate skills, team, and OpenClaw.
custom-promptsstringPath to a directory that extends or overrides OMX default prompts
approval_policystringTool-call approval policy: "suggest", "auto-edit", or "full-auto"
model = "gpt-4.1"
codex_hooks = true
custom-prompts = "~/.codex/prompts"
approval_policy = "auto-edit"

.codex/hooks.json

Registers hook handlers that run at each lifecycle point. Each entry maps a hook name to a command or MCP tool.

{
  "hooks": {
    "session-end": {
      "command": "~/.codex/scripts/on-session-end.sh {{sessionId}}"
    }
  }
}

For the full hook catalog, see the upstream repository.

CLI Flags

FlagDescription
--madmaxMaximum parallelism mode — spawns the full team pipeline automatically.
--highHigh-effort mode — uses the highest-tier model available.
--skip-git-repo-checkSuppresses the error when launching outside a git repository.
--sparkRoutes team workers through the spark worker tier.
--madmax-sparkCombines --madmax with spark worker routing.

On this page