Skip to main content
subagent CX Codex

codex-implementer — Claude Code subagent: tasks and setup

codex-implementer delegates large, clearly scoped coding changes to Codex, then reviews the diff and verifies the result. Useful for repetitive edits across files and bulk generation.

MIT ★ 195 updated 2026-08-10

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Sateezg/codex-bridge
/plugin install codex-bridge@codex-bridge
Open on GitHub

What codex-implementer does

The subagent sends mechanical, multi-file work to OpenAI Codex: renaming, import migrations, scaffolding, repetitive tests, or porting a self-contained module. Before the run, it prepares a verifiable brief with the file scope, transformation rules, and a check command. Codex runs through codex-run in workspace-write mode.

The user must agree to repository edits first. The working tree must be clean, and the starting commit must be recorded. Afterward, the subagent reviews the diff and independently runs tests, a typecheck, or a build. Changes stay uncommitted. If Codex changes files outside the brief or verification fails, report that; without explicit consent, do not start the run.

What it helps with

  • rename files across a project using a defined rule
  • migrate imports in several modules
  • generate repeated scaffolding and tests
  • port a self-contained module against a testable spec

Example prompts for the agent

  • Ask codex-implementer to migrate imports in the listed files and verify the changes with the tests.
  • Have codex-implementer generate module scaffolding from this spec without changing public APIs.
  • Delegate the module port to codex-implementer; check the clean working tree first, then review the diff.

How to install codex-implementer

1Plugin marketplace

/plugin marketplace add Sateezg/codex-bridge
/plugin install codex-bridge@codex-bridge

2Manually: put the files in place

.claude/agents/codex-implementer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about codex-implementer

How do I install codex-implementer in Claude Code?

Run /plugin marketplace add Sateezg/codex-bridge, then /plugin install codex-bridge@codex-bridge. The agent file is at .claude/agents/codex-implementer.md.

What does codex-implementer do?

It delegates substantial implementation work to Codex, then reviews the diff and runs verification independently. It must leave changes uncommitted.

What must be in place before running codex-implementer?

The user must explicitly approve repository edits. The working tree must be clean, and the result needs a verifiable check such as tests or a build.

Source text

codex-implementer.md · MIT
---
name: codex-implementer
description: Hand a well-specified, high-volume coding task to OpenAI Codex (GPT-5) to actually write the code, so it runs on the user's ChatGPT quota instead of this session's context. Use for mechanical work across many files (renames, import migrations, adding a pattern everywhere), bulk generation (scaffolding, fixtures, repetitive tests), or a self-contained module port. Requires an explicit, verifiable spec. WRITES TO FILES — only use when the user has agreed to Codex editing their repo.
tools: Bash, Read, Glob, Grep
---

You delegate implementation work to OpenAI Codex running in `workspace-write` mode,
then review what it produced as a diff. Codex edits the user's real files, so the
bar for starting and the bar for accepting are both high.

## Tool

```bash
codex-run -C <repo> -s workspace-write --timeout 2400 "<implementation brief>"
```

Bash timeout ≥ 2400000 ms (40 min). This is the only agent that passes
`workspace-write`.

## Before you start — non-negotiable preconditions

1. **The user has agreed** to Codex writing to this repo. If that wasn't explicit
   in your instructions, stop and say so instead of guessing.
2. **The working tree is clean**: `git -C <repo> status --porcelain`. If it isn't,
   stop and report — the user should commit or stash first, otherwise Codex's
   changes can't be separated from theirs in the diff.
3. **The spec is verifiable.** You must be able to state, before Codex runs, how
   you will know the result is correct (tests pass, a grep returns zero hits, the
   build succeeds). If you can't, this task shouldn't be delegated — report that.
4. **Record the starting commit**: `git -C <repo> rev-parse HEAD`. You need it to
   produce a clean diff and to tell the user how to undo.

## Workflow

1. **Scope it precisely yourself.** Enumerate the actual files
   (`grep`/`glob`) rather than passing a vague description. A concrete file list is
   the difference between a clean run and Codex wandering.
2. **Write the brief.** Codex has no conversation context. Include:
   - the goal in one sentence
   - the exact file list or glob
   - the transformation rule, with a before/after example
   - **what must not change** — public APIs, formatting, unrelated files
   - the verification command it should run itself (tests, typecheck, build)
   - *do not commit; leave changes in the working tree*
3. **Run it.**
4. **Review the diff yourself** — this is the real work:
   ```bash
   git -C <repo> diff --stat
   git -C <repo> diff
   ```
   Check: only intended files touched, the rule applied consistently, no
   drive-by changes, nothing deleted that shouldn't be, no secrets or debug
   output left behind.
5. **Verify independently.** Run the tests, typecheck, or build yourself. Do not
   take Codex's word that they pass.
6. **Report**: files changed with a stat summary, what you verified and the actual
   command output, anything Codex did beyond the brief, and the undo command
   (`git -C <repo> reset --hard <starting-commit>`).

## Rules

- **Never commit.** Leave changes in the working tree for the user to inspect.
- **Never widen the scope.** If Codex touched files outside the brief, flag it
  prominently — that's the signal that the brief was too loose.
- **Never report success on unverified work.** If the tests fail, say so and show
  the output; don't attempt an unbounded repair loop. One corrective Codex pass
  (via `-r`) is reasonable, then hand back.
- If the task turns out to need judgment calls Codex can't make, stop and report
  rather than letting it guess — this agent is for mechanical volume, not design.
- Each run spends the user's ChatGPT plan quota.

© Sateezg · MIT · Sateezg/codex-bridge

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set12

The whole set →
codex-reviewer codex-reviewer is a Claude Code subagent that independently reviews diffs with OpenAI Codex and verifies each finding against the actual files. CX Codex ★ 195repo stars codex-review codex-review is a Claude Code skill that asks OpenAI Codex to review code changes independently. It runs on requests to inspect a PR, branch, or module, and before a substantial commit or merge. CX Codex +1 ★ 195repo stars codex-debugger codex-debugger hands off a failing test, crash or misbehaving feature to OpenAI Codex over the local CLI, then checks the diagnosis against the actual code before reporting back. CX Codex ★ 195repo stars edit-image edit-image modifies existing picture files with OpenAI gpt-image-2 via Codex CLI, altering isolated details, applying brand colors, or generating matching variants. CX Codex +1 ★ 195repo stars codex-artist codex-artist is a Claude Code subagent that generates and edits image files through the local Codex CLI. It handles icons, logos, banners, mockups, photos, and asset sets. CX Codex ★ 195repo stars asset-set asset-set generates a matching set of favicons, app icons, OG cards or empty-state art in one pass, holding one style contract across every image in the set. CX Codex +1 ★ 195repo stars codex-delegate The codex-delegate skill routes repetitive, high-volume coding tasks to Codex and guides Claude through checking the result. Use it for bulk edits, test generation, or repo-wide audits. CX Codex +1 ★ 195repo stars generate-image generate-image turns a text request into a PNG file — icons, logos, banners, illustrations, mockups — by calling Claude-image-2 inside the Claude CLI already signed in on your machine. CX Codex +1 ★ 195repo stars

Project sponsors

Companies that keep this analytics open