Claude + Codex

README.md

Enable Codex from Claude Code

source: https://x.com/theo/status/2072482460122964067

You can run Codex from inside Claude Code by installing OpenAI’s Claude Code plugin for Codex, then invoking the /codex:* commands from within your Claude session. The plugin uses your existing local Codex CLI auth and config, so since you already have both installed, setup should be quick.

Setup

Run these inside Claude Code:

1. Add the plugin marketplace:

/plugin marketplace add openai/codex-plugin-cc

2. Install the plugin:

/plugin install codex@openai-codex

3. Reload plugins:

/reload-plugins

4. Verify setup:

/codex:setup

The plugin’s setup flow and verification command are documented as the intended path for getting Codex working inside Claude Code. youtube

Useful commands

After setup, these are the main commands you’ll likely use:

• /codex:review for a standard review.
• /codex:adversarial-review for a more skeptical audit.
• /codex:rescue when you want Codex to investigate a problem.
• /codex:status to check a background job.
• /codex:result to fetch the finished output.
• /codex:cancel to stop a running task. youtube

A common first test is:

/codex:review --background
/codex:status
/codex:result

That starts a background review, lets you check progress, and then pulls the findings once it finishes. youtube

If it does not work

If /codex:setup says Codex is missing or not authenticated, re-check that the local CLI works first with codex and codex login, then rerun the plugin setup. The plugin relies on the local Codex CLI rather than a separate runtime, so fixing the CLI auth usually resolves setup issues. reddit

CLAUDE.md

@AGENTS.md

Picking the right models for workflows and subagents

Rankings, higher = better. Cost reflects what I actually pay (OpenAI has really generous limits), not list price. Intelligence is how hard a problem you can hand the model unsupervised. Taste covers UI/UX, code quality, API design, and copy.

model	cost	intelligence	taste
gpt-5.5	9	8	5
sonnet-5	5	5	7
opus-4.8	4	7	8
fable-5	2	9	9

How to apply:

• These are defaults, not limits. You have standing permission to override them: if a cheaper model's output doesn't meet the bar, rerun or redo the work with a smarter model without asking. Judge the output, not the price tag. Escalating costs less than shipping mediocre work.
• Cost is a tie-breaker only; when axes conflict for anything that ships, intelligence > taste > cost.
• Bulk/mechanical work (clear-spec implementation, data analysis, migrations): gpt-5.5 - it's effectively free.
• Anything user-facing (UI, copy, API design) needs taste ≥ 7.
• Reviews of plans/implementations: fable-5 or opus-4.8, optionally gpt-5.5 as an extra independent perspective.
• Never use Haiku.
• Mechanics: gpt-5.5 is only reachable through the Codex CLI - codex exec / codex review (my ~/.codex/config.toml defaults to gpt-5.5). Use the codex-implementation, codex-review, and codex-computer-use skills; for work they don't cover (investigation, data analysis), run codex exec -s read-only directly with a self-contained prompt.
• Claude models (sonnet-5, opus-4.8, fable-5) run via the Agent/Workflow model parameter.

Using gpt-5.5 inside workflows and subagents (the model parameter only takes Claude models, so use a wrapper):

• Spawn a thin Claude wrapper agent with model: 'sonnet', effort: 'low' whose prompt instructs it to write a self-contained codex prompt, run codex exec via Bash, and return