Codex

grith exec --profile codex -- codex

The codex profile fits OpenAI's Codex CLI. Similar surface area to claude-code — full home access, shell, network, exec — but with codex-specific routine paths and destinations.

What it routinely allows

• Paths — ${PROJECT_DIR}/**, ${HOME}/.cache/codex/**, ${HOME}/.config/codex/**, ${HOME}/.openai/**, /tmp/codex-**.
• Commands — same toolchain set as Claude Code (git, npm, cargo, python, gh, etc.) plus codex itself when nested.
• Destinations — api.openai.com, chatcompletions.openai.com, package registries (registry.npmjs.org, pypi.org, crates.io), github.com, *.githubusercontent.com.
• Exec roots — same baseline as Claude Code.

Differences from claude-code

The main differences are the cache/config locations and the API host. Otherwise the two profiles are structurally similar.

For agents that wrap both providers (multi-model), use claude-code if the underlying tool is Claude Code with Codex as a fallback, or vice versa — they're close enough.

Tuning

Same patterns as Claude Code:

[profiles.my-codex]
extends = "codex"
routine_destinations = ["acme-openai-proxy.internal"]

See also

• Claude Code profile — close cousin
• Built-in profiles
• How profiles work