openai/codex-plugin-cc Instruction Manual

What openai/codex-plugin-cc is—in plain language

Official OpenAI Claude Code plugin for Codex read-only/adversarial reviews, rescue delegation, session transfer, and background job management.

Mental model: This repository provides a directly runnable command or package. You give the command an input, it performs the documented workflow, and it returns files, terminal output, a local interface, or a remote result.

Interfacesplugin, slash commands

Primary languageNone documented

Typical useGet a Codex second opinion from Claude Code, delegate a stuck task, or transfer session context to Codex.

Your first 15 minutes

Complete the linked Installation Guide and its verification step.
Create a disposable test folder or use non-sensitive sample data.
Run the small example below and observe what files, ports, or prompts appear.
Read the result before approving writes, network calls, account access, or costs.
Only then repeat the workflow with a real project.

Starter workflow

/codex:rescue investigate why the tests started failing
/codex:rescue fix the failing test with the smallest safe patch
/codex:rescue --resume apply the top fix from the last run
/codex:rescue --model gpt-5.4-mini --effort medium investigate the flaky integration test
/codex:rescue --model spark fix the issue quickly
/codex:rescue --background investigate the regression

Open Installation Guide Open upstream README

Complete indexed functionality map

Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.

/codex:review

command

Read-only Codex review.

README.md

Open component record →

/codex:adversarial-review

command

Challenge assumptions/risks.

README.md

Open component record →

/codex:rescue

command

Delegate investigation/fix.

README.md

Open component record →

codex-rescue

sub_agent

Run delegated Codex task.

README.md

Open component record →

/codex:transfer

command

Import Claude session into Codex.

README.md

Open component record →

status/result/cancel

command

Manage background Codex jobs.

README.md

Open component record →

Upstream feature-by-feature guide

These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.

Upstream capability

What You Get

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns what you get. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Requirements

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns requirements. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:review

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:review. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:adversarial-review

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:adversarial-review. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:rescue

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:rescue. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:transfer

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:transfer. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:status

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:status. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:result

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:result. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

/codex:cancel

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns /codex:cancel. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Codex Integration

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns codex integration. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Common Configurations

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns common configurations. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

Upstream capability

Moving The Work Over To Codex

Upstream treats this as a distinct part of openai/codex-plugin-cc. In plain language, use this area when your task concerns moving the work over to codex. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.

How to use the main workflows

Choose the smallest relevant function

Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.

Prepare a disposable input

Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.

Run, observe, and stop

Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.

Inspect the result

Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.

Save a repeatable recipe

Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.

Copy-paste recipes from upstream documentation

These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.

/codex:rescue

/codex:rescue investigate why the tests started failing
/codex:rescue fix the failing test with the smallest safe patch
/codex:rescue --resume apply the top fix from the last run
/codex:rescue --model gpt-5.4-mini --effort medium investigate the flaky integration test
/codex:rescue --model spark fix the issue quickly
/codex:rescue --background investigate the regression

Start Something Long-Running

/codex:adversarial-review --background
/codex:rescue --background investigate the flaky test

Start Something Long-Running

/codex:status
/codex:result

Configuration, accounts, and files

Configuration files

None documented

A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.

Important directories

None documented

Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.

Credentials

ChatGPT subscription or OpenAI API key/Codex login

Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.

External services

OpenAI Codex

Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.

Safe operating habits

Use test data first and keep a current backup or Git commit.
Read commands before pasting. A README is useful evidence, not a substitute for judgment.
Review agent-generated file changes with git diff before committing.
Keep local services bound to 127.0.0.1 unless you intentionally secure and expose them.
Do not give plugins or MCP servers broader filesystem, browser, GitHub, or cloud access than their current task requires.
Confirm API costs and model names before running large batches.
Stop and investigate repeated authentication failures instead of pasting a token into multiple places.

Reference and source trail

The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.