Skip to main content
plugin CX Codex

cc — Claude Code plugin: what it does, how to install

cc runs Claude Code reviews, architecture checks, and rescue tasks directly from Codex sessions with tracked background jobs.

Apache-2.0 ★ 1,596 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install cc@awesome-codex-plugins
Open on GitHub

What cc does

The plugin bridges Codex and Claude Code so you can offload work without switching editors. Codex keeps conversational control, while Claude Code handles diff reviews, exploratory fixes, or architecture challenges using commands such as $cc:review, $cc:adversarial-review, and $cc:rescue. Background runs execute as session-scoped jobs with lifecycle status and output inspection through $cc:result.

Operation requires Node.js 18+, Codex with native hook support, and a working @anthropic-ai/claude-code installation authenticated with claude auth login. Without the authenticated Claude CLI, background reviews will not execute.

What it helps with

  • run read-only diff reviews with $cc:review
  • challenge assumptions and tradeoffs via $cc:adversarial-review
  • hand bug investigations and fixes to Claude Code using $cc:rescue
  • monitor background execution with $cc:status

Example prompts for the agent

  • $cc:review --background
  • $cc:adversarial-review
  • $cc:status

How to install cc

Plugin marketplace

/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install cc@awesome-codex-plugins

Step by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own

Questions about cc

How to install cc in Claude Code?

Add the marketplace source with /plugin marketplace add hashgraph-online/awesome-codex-plugins, then run /plugin install cc@awesome-codex-plugins.

What does cc do?

It lets Codex host Claude Code workflows, delegating diff reviews, adversarial audits, and bug fix investigations to Claude models.

What are the prerequisites for cc?

You need Node.js 18+, Codex with hook support enabled, and the Claude CLI authenticated through claude auth login.

Source text

cc-plugin-codex · Apache-2.0
<p align="center">
  <img src="assets/cc-plugin-codex-logo.svg" height="128" alt="cc-plugin-codex" />
</p>

<h3 align="center">Claude Code Plugin for Codex</h3>

<p align="center">
  Run Claude Code reviews, rescue tasks, and tracked background work from inside Codex.
</p>

<p align="center">
  <code>cc-plugin-codex</code> runs inside Codex and lets you use Claude Code and Claude models for review, rescue, and tracked background workflows.
</p>

<p align="center">
  <a href="#quick-start"><strong>Quick Start</strong></a> ·
  <a href="#commands"><strong>Commands</strong></a> ·
  <a href="#background-jobs"><strong>Background Jobs</strong></a> ·
  <a href="#review-gate"><strong>Review Gate</strong></a> ·
  <a href="#how-this-differs-from-upstream"><strong>vs Upstream</strong></a> ·
  <a href="https://github.com/sendbird/cc-plugin-codex/issues"><strong>Issues</strong></a>
</p>

---

## What Is This?

`cc-plugin-codex` turns Codex into a host for Claude Code work.
**Codex stays in charge of the thread. Claude Code does the review and rescue work.**

You get seven commands (`$cc:review`, `$cc:adversarial-review`, `$cc:rescue`, `$cc:status`, `$cc:result`, `$cc:cancel`, `$cc:setup`) that launch tracked Claude Code work, manage lifecycle and ownership, and surface results back into Codex.

That includes:
- Built-in Codex subagent orchestration for rescue and background review flows
- Session-scoped tracked jobs with status, result, and cancel commands
- Background completion nudges that steer you to the right `$cc:result <job-id>`
- An optional turn-end review gate
- GitHub CI coverage on Windows, macOS, and Linux

It follows the shape of [openai/codex-plugin-cc](https://github.com/openai/codex-plugin-cc) but runs in the opposite direction.

## Quick Start

### 1. Install

Install from the Sendbird marketplace:

```bash
codex plugin marketplace add sendbird/codex-marketplace
codex plugin add cc@sendbird
```

Then install `cc` from the Sendbird marketplace inside Codex, and run `$cc:setup` once.

`cc-plugin-codex` uses Codex native plugin hooks. The active plugin copy lives under Codex's plugin cache, and hook commands resolve through `$PLUGIN_ROOT`; there is no separate local checkout install.

The optional `npx` helper runs the same marketplace/cache install path and enables the required Codex feature gates:

```bash
npx cc-plugin-codex install
```

On Windows, prefer the Sendbird marketplace path or the `npx` helper. The shell-script helper below is POSIX-only.
Codex CLI's official guidance still treats Windows support as experimental and recommends a WSL workspace for the best Codex experience. Claude Code supports both native Windows and WSL.

> **Prerequisites:** Node.js 18+, Codex with hook support, and `claude` CLI installed and authenticated.
> If you don't have the Claude CLI yet:
> ```bash
> npm install -g @anthropic-ai/claude-code && claude auth login
> ```

### 2. Verify

Open Codex and run:

```text
$cc:setup
```

All checks should pass. If any fail, `$cc:setup` tells you what to fix.
If setup adds the marketplace-qualified plugin-data root and legacy migration roots to the writable-root list, restart Codex and rerun the same command; a requested review-gate toggle waits for that restart.

### 3. Try It

```text
$cc:review --background
```

That launches a Claude Code review from a Codex-managed background flow. You can check on it immediately:

```text
$cc:status
$cc:result
```

When it finishes, Codex should nudge you toward the right result. If not, `$cc:status` and `$cc:result` are always the fallback.

## Commands

| Command | What It Does |
| --- | --- |
| `$cc:review` | Read-only Claude Code review of your changes |
| `$cc:adversarial-review` | Design-challenging review — questions approach, tradeoffs, hidden assumptions |
| `$cc:rescue` | Hand a task to Claude Code — bugs, fixes, investigations, follow-ups |
| `$cc:status` | List running and recent Claude Code jobs, or inspect one job |
| `$cc:result` | Open the output of a finished job |
| `$cc:cancel` | Cancel an active background job |
| `$cc:setup` | Verify installation, auth, hooks, and review gate |

Quick routing rule:
- Use `$cc:review` for straightforward correctness review of the current diff.
- Use `$cc:adversarial-review` for riskier config/template/migration/design changes, or whenever you want stronger challenge on assumptions and tradeoffs.
- Use `$cc:rescue` when you want Claude Code to investigate, validate by changing code, or actually fix/implement something.

### `$cc:review`

Standard read-only review of your current work.

```text
$cc:review                          # review uncommitted changes (default: opus)
$cc:review --base main              # review branch vs main
$cc:review --scope branch           # explicitly compare branch tip to base
$cc:review --background             # run in background, check with $cc:status later
$cc:review --model sonnet           # switch to sonnet
$cc:review --model fable            # use Fable
$cc:review --model opus --effort xhigh  # explicitly raise opus effort
```

**Flags:** `--base <ref>`, `--scope <auto|working-tree|branch>`, `--wait`, `--background`, `--model <model>`, `--effort <low|medium|high|xhigh|max>`

**Defaults:** model `opus`, and no effort at all. After trimming surrounding whitespace, the friendly aliases `fable`, `opus`, `sonnet`, and `haiku` are matched case-insensitively and canonicalized to lowercase; every other `--model` value passes through unchanged for Claude Code to resolve, including full model IDs and provider-specific names. `--effort` is forwarded only when you pass it, so each model keeps whatever effort Claude Code defaults to. Claude Code owns which effort levels each model supports, so check `/model` rather than assuming a level applies everywhere.

**Model discovery:** run `/model` in Claude Code to see the models and effort levels available to your current account and provider, then pass the selected alias or full ID to this plugin. The plugin intentionally does not maintain a static model catalog, a per-model effort table, or force `[1m]`; Claude Code owns alias versions, supported effort levels, managed restrictions, provider routing, and extended-context eligibility.

Scope `auto` (the default) inspects `git status` and chooses between working-tree and branch automatically.

In foreground, review returns the result directly. In background, the plugin uses a Codex built-in subagent, tracks the review as a job, and nudges you to open the result when it completes.

If the diff is too large to inline safely, the review prompt falls back to concise status/stat context and tells Claude to inspect the diff directly with read-only `git diff` commands instead of failing the run.

### `$cc:adversarial-review`

Same as `$cc:review`, but steers Claude to challenge the implementation — tradeoffs, alternative approaches, hidden assumptions.

```text
$cc:adversarial-review
$cc:adversarial-review --background question the retry and rollback strategy
$cc:adversarial-review --base main challenge the caching design
```

Accepts the same flags as `$cc:review`, plus free-text focus after flags to steer the review.

Background adversarial review uses the same tracked built-in subagent pattern as `$cc:review`.

### `$cc:rescue`

Hand a task to Claude Code. This is the main way to delegate real work — bug fixes, investigations, refactors.

```text
$cc:rescue investigate why the tests started failing
$cc:rescue fix the failing test with the smallest safe patch
$cc:rescue --resume apply the top fix from the last run
$cc:rescue --background investigate the regression
$cc:rescue --model sonnet --effort medium investigate the flaky test
```

**Flags:**

| Flag | Description |
| --- | --- |
| `--background` | Run in background; check later with `$cc:status` |
| `--wait` | Run in foreground |
| `--resume` | Continue the most recent Claude Code task |
| `--resume-last` | Alias for `--resume` |
| `--fresh` | Force a new task (don't resume) |
| `--write` | Allow file edits (default) |
| `--model <model>` | Any Claude Code model alias, full model ID, or provider-specific name; defaults to `opus`. Run `/model` in Claude Code to discover options available to your account and provider. |
| `--effort <level>` | Reasoning effort: `low`, `medium`, `high`, `xhigh`, `max`. Unset by default, so the model keeps Claude Code's own effort default. Claude Code owns which levels each model supports. |
| `--prompt-file <path>` | Read task description from a file |

**Resume behavior:** If you don't pass `--resume` or `--fresh`, rescue checks for a resumable Claude session and asks once whether to continue or start fresh. Your phrasing guides the recommendation — "continue the last run" → resume, "start over" → fresh.

Background rescue runs through a built-in Codex subagent. When the child finishes, the plugin tries to nudge the parent thread with the exact `$cc:result <job-id>` to open.

### `$cc:status`

```text
$cc:status                          # list active and recent jobs
$cc:status task-abc123              # detailed status for one job
$cc:status --all                    # show all tracked jobs in this repository workspace
$cc:status --wait task-abc123       # block until job completes
```

By default, `$cc:status` shows jobs owned by the current Codex session. Use `--all` when you want the wider repository view across older or sibling sessions in the same workspace.

### `$cc:result`

```text
$cc:result                          # open the latest finished job for this session/repo
$cc:result task-abc123              # show finished job output
```

When a job came from a built-in background child, the output can show both:
- the **Claude Code session** you can resume with `claude --resume ...`
- the **Owning Codex session** that owns the tracked job inside Codex

To reopen the Claude Code session directly:

```bash
claude --resume <session-id>
```

### `$cc:cancel`

```text
$cc:cancel task-abc123              # cancel a running job
```

### `$cc:setup`

```text
$cc:setup                           # verify everything
$cc:setup --enable-review-gate      # turn on turn-end review gate
$cc:setup --disable-review-gate     # turn it off
```

Setup checks Claude Code availability, native plugin hook feature gates, and review-gate state. If Claude Code isn't installed, it offers to install it.
This is also the repair path for marketplace-installed copies of the plugin: `$cc:setup` confirms `[features].hooks = true`, trusts this plugin's current native hook hashes, and allows sandboxed writes to Codex's injected marketplace-qualified plugin-data root plus the legacy roots needed for one-time migration. If those writable roots were just added, restart Codex and rerun setup before changing the review gate.

## Background Jobs

All review and rescue commands support `--background`. Background jobs are tracked per-session with full lifecycle management:

1. **Queued → Running → Completed** — jobs progress through states automatically.
2. **Built-in subagent background flows** — background rescue, review, and adversarial review use Codex-managed subagent turns rather than stuffing `--background` into the companion command itself.
3. **Completion nudges** — when a background built-in flow finishes, the plugin tries to nudge the parent thread with the right `$cc:result <job-id>`. If that nudge cannot surface cleanly, unread-result hooks are the backstop.
   The nudge is intentionally just a pointer. The actual stored result still opens through `$cc:result`.
4. **Unread-result fallback** — when you submit your next prompt after a finished unread job, Codex can remind you that a result is waiting and point you to `$cc:status` / `$cc:result`.
5. **Session ownership** — jobs stay attached to the user-facing parent Codex session even when a built-in rescue/review child does the actual work, so plain `$cc:status`, `$cc:result`, and resume-candidate detection still follow the parent thread.
6. **Cleanup on exit** — when your Codex session ends, any still-running detached jobs are terminated via PID identity validation, and stale reserved job markers are cleaned up over time.

**Typical background flow:**

```text
$cc:rescue --background investigate the performance regression
# ... keep working ...
# Codex nudges with the exact result command when possible
$cc:result task-abc123
```

### What “background” means here

- The parent Codex thread does not wait.
- The Claude companion command still runs in the foreground inside its own worker/subagent thread.
- For rescue and background review flows, the plugin prefers Codex built-in subagents and only uses job polling/status commands as the durable backstop.

## Review Gate

The review gate is an **optional turn-end hook**. When enabled, Codex runs a Claude Code review of the last Codex response before the turn is allowed to finish.

- Claude returns `ALLOW:` → the turn finishes normally.
- Claude returns `BLOCK:` → the turn is blocked; Codex continues with the review feedback.

**Caveats:**

- **Disabled by default.** Enable with `$cc:setup --enable-review-gate`.
- **Uses your Claude Code defaults.** The gate does not pass `--model` or `--effort`; set your preferred default in Claude Code if you want the gate to use a specific model or effort level.
- **Token cost.** Every edit-producing turn can trigger a Claude invocation. This can drain usage limits quickly in active coding sessions.
- **15-minute timeout.** The gate has a hard timeout. If Claude doesn't respond, the turn remains blocked and the error points you to a manual review.
- **Skip-on-no-edits.** The gate computes a working-tree fingerprint baseline and skips review when the last Codex turn made no net edits.
- **Not in nested sessions.** Child sessions (e.g., rescue subagents) suppress the gate to avoid feedback loops.

**Only enable when you're actively monitoring the session.**

## How This Differs From Upstream

| | [openai/codex-plugin-cc](https://github.com/openai/codex-plugin-cc) | This repository |
| --- | --- | --- |
| **Host** | Claude Code hosts the plugin | Codex hosts the plugin |
| **Commands** | `/codex:review`, `/codex:rescue`, … | `$cc:review`, `$cc:rescue`, … |
| **Runtime** | Codex app-server + broker | Fresh `claude -p` subprocess per invocation |
| **Review gate trigger** | End of Claude Code turn | End of Codex turn |
| **Review gate target** | Reviews previous Claude response | Reviews previous Codex response |
| **Model flags** | Codex model names and effort controls | Claude model names and effort values (`low` / `medium` / `high` / `xhigh` / `max`) |

### Where This Goes Further

- **Smart review gate** — fingerprints the working tree and skips turn-end review when the last Codex turn made no net edits, avoiding unnecessary token spend.
- **Nested-session awareness** — suppresses turn-end review and unread-result prompts in child runs, keeping interactive hooks attached to the user-facing thread only.
- **Tracked job ownership** — background jobs track unread/viewed state and session ownership, with safe PID-validated cleanup on session exit.
- **Built-in background notify** — rescue and review flows can now wake the parent thread and point directly to `$cc:result <job-id>` instead of relying only on later polling.
- **Unread-result nudges** — completed background jobs are still surfaced in your next prompt as a reliable fallback.
- **Idempotent installer** — installs through Codex's marketplace/cache path and enables native hook feature gates. Safe to re-run for updates.

## Install Variants

### Sendbird marketplace (preferred)

Add the marketplace:

```bash
codex marketplace add sendbird/codex-marketplace
```

Then install `cc` from the Sendbird marketplace inside Codex, and run:

```text
$cc:setup
```

Marketplace/plugin install places the plugin under Codex's plugin cache. `$cc:setup` verifies Claude Code, confirms `[features].hooks = true`, and trusts the current `hooks/hooks.json` hook hashes from the active plugin cache.

### npx helper

```bash
npx cc-plugin-codex install
```

After install, run:

```text
$cc:setup
```

The helper adds the Sendbird marketplace, installs `cc` through Codex app-server, enables native hook feature gates, and removes stale global hook entries from older installs.

### Shell script (POSIX-only)

```bash
curl -fsSL "https://raw.githubusercontent.com/sendbird/cc-plugin-codex/main/scripts/install.sh" | bash
```

After install, run:

```text
$cc:setup
```

### Update

Re-run the marketplace update/install flow or the `npx` helper — both are idempotent.

```bash
npx cc-plugin-codex update
```

### Uninstall

```bash
npx cc-plugin-codex uninstall
```

## Troubleshooting

**`$cc:setup` reports Claude Code not found**
```bash
npm install -g @anthropic-ai/claude-code
claude auth login
```

**Commands not recognized in Codex**
Re-run install and restart Codex. This plugin expects Codex plugin support and no longer installs local skill-wrapper fallbacks.

**Hooks not firing**
Check that `hooks = true` is set in `~/.codex/config.toml` under `[features]`. Run `$cc:setup` to verify and auto-repair the feature gate plus this plugin's hook trust hashes, then restart Codex if that flag was just changed.

**A background job finished but I did not get the result nudge**
Use:
```text
$cc:status
$cc:result
```
The built-in notify path is best-effort. The tracked job store and unread hook remain the reliable fallback.

If you think the job may belong to an older session in the same repository, use:
```text
$cc:status --all
```

If a finished result shows both a **Claude Code session** and an **Owning Codex session**, use the Claude Code session for `claude --resume ...`. The owning session is there only to explain which Codex thread owns the tracked job.

**Large review diff caused a failure or was omitted**
That is expected on very large diffs. The plugin now degrades to a compact review context and points Claude toward read-only `git diff` commands instead of trying to inline everything. If you want the full picture, run a narrower review such as:
```text
$cc:review --base main
$cc:review --scope working-tree
```

**Review gate draining tokens**
Disable it: `$cc:setup --disable-review-gate`. The gate can fire after every edit-producing turn, which adds up.

**Background jobs not cleaned up**
Jobs are terminated when the Codex session that owns them exits. If a session crashes without cleanup, use `$cc:status` and `$cc:cancel <job-id>` to clean up any leftovers.

## License

[Apache-2.0](LICENSE) — see [NOTICE](NOTICE) for attribution.

© Sendbird, Inc. · Apache-2.0 · hashgraph-online/awesome-codex-plugins

Similar plugins

All plugins for Code review and refactoring →
ub-mode unclebob The ub-mode skill for Claude Code helps developers structure code changes. It guides the development process by following the principles of "First Make it Work, Then Make it Right, Then Follow Practice." CX Codex +1 930installs methodology-advisor FlorianBruniaux The methodology-advisor command for Claude Code and Codex reads the codebase and asks three questions to recommend an AI-development methodology stack. Run it at the start of a project, before choosing a workflow. CX Codex +1 ★ 6,529repo stars superpowers obra superpowers — a plugin for Claude Code and Codex that teaches the agent a complete methodology: requirements gathering, design, TDD, and subagent-driven development. Triggers automatically when you start building something new. CX Codex ★ 323,788repo stars ponytail DietrichGebert ponytail is a Claude Code plugin that steers coding tasks toward short, practical solutions. Its review command checks related code for bugs, security issues, and missing tests. ★ 196,420repo stars mattpocock-skills Matt Pocock mattpocock-skills — a set of skills for grilling, TDD, code review, and specification work. Use it when an agent needs to clarify the task before changing the code. ★ 329,816repo stars understand-anything Egonex-AI understand-anything turns codebases or markdown wikis into an interactive knowledge graph with a browser dashboard. Helps navigate unfamiliar repositories without reading files blindly. ★ 93,566repo stars serena official Oraios serena — a Claude Code plugin that integrates language server protocol for semantic analysis. Provides refactoring suggestions, code navigation, and symbol lookups across the codebase. ★ 47,914repo stars security-guidance official Anthropic security-guidance — a Claude Code plugin that reviews generated code in three layers. Regex warnings fire on edits, an LLM checks the diff after every turn, and an agentic reviewer walks related files before commits. ★ 47,914repo stars

From the same set391

The whole set →
clean-room clean-room separates authorized source analysis from clean implementation work. Use it to create behavioral specifications without carrying source material into destination code. CX Codex ★ 1,596repo stars claudemon claudemon turns your Claude agents into pixel creatures you can watch work in your files, with a one-click .io brawler called Clawland for breaks. CX Codex ★ 1,596repo stars claude-code-skills This plugin gives Claude Code reusable instructions and workflows for engineering and other tasks. It also includes Python tools and reference materials. CX Codex ★ 1,596repo stars claude-code-harness claude-code-harness turns a vague agent idea into a runtime blueprint: request assembly, the turn loop, tool permissions, memory and recovery. CX Codex ★ 1,596repo stars claude-code A local MCP bridge connects Codex to an authenticated Claude Code CLI. Use it to check account status, sign in, or run workspace prompts in safe modes. CX Codex ★ 1,596repo stars chatgpt-agent chatgpt-agent is a Claude Code and Codex plugin that brings ChatGPT into review, planning, editing, and implementation tasks. It uses ZIP, MCP, or GitHub access. CX Codex ★ 1,596repo stars casefile casefile tracks persistent security findings for bug bounties and CTFs with isolated Docker PoC validation. CX Codex ★ 1,596repo stars bringyour-migration-auditor bringyour-migration-auditor runs a read-only check on a project that just moved from Claude to Claude: rule files, hooks, MCP config, skills, secret references. Use it before the agent edits code. CX Codex ★ 1,596repo stars

Project sponsors

Companies that keep this analytics open