https://github.com/yujingz/use-claude-code-from-codex
Use local Claude Code from Codex as a second opinion, reviewer, or parallel coding agent.
https://github.com/yujingz/use-claude-code-from-codex
agent-skills ai-agents anthropic claude claude-code code-review codex codex-skill developer-tools openai-codex
Last synced: 5 days ago
JSON representation
Use local Claude Code from Codex as a second opinion, reviewer, or parallel coding agent.
- Host: GitHub
- URL: https://github.com/yujingz/use-claude-code-from-codex
- Owner: yujingz
- Created: 2026-06-17T10:10:06.000Z (19 days ago)
- Default Branch: master
- Last Pushed: 2026-06-17T14:17:56.000Z (18 days ago)
- Last Synced: 2026-06-17T16:34:47.685Z (18 days ago)
- Topics: agent-skills, ai-agents, anthropic, claude, claude-code, code-review, codex, codex-skill, developer-tools, openai-codex
- Language: JavaScript
- Size: 63.5 KB
- Stars: 1
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Claude from Codex
[](https://developers.openai.com/codex/skills)
[](https://www.anthropic.com/claude-code)
[](#install)
[](#install)
[](docs/companion-cli.md)
Use local Claude Code from Codex for second opinions, code review, and parallel investigation without leaving your Codex session.
Prerequisite: Claude Code should already work on your machine.
Works as a plain skill folder. No Codex plugin login or marketplace packaging is required.
## 30 Second Start
Paste this into Codex UI or Codex CLI:
```text
Install the Codex skill from https://github.com/yujingz/use-claude-code-from-codex.
Prefer the vercel-labs/skills installer if it is available.
Install the skill named claude-from-codex for Codex, then verify that $claude-from-codex is discoverable.
```
Then ask:
```text
Use $claude-from-codex to ask Claude for a read-only review of my current diff.
Focus on bugs, security issues, and missing tests.
```
## Use It For
These examples use this repo's own workflow, but the same pattern works in any project.
| Real situation | What to ask Codex |
| --- | --- |
| You changed the worker state-root logic and want another model to check it | `Use $claude-from-codex to review the current diff around jobs.mjs and state.mjs. Check whether background workers still find jobs when XDG_STATE_HOME is set.` |
| A documentation PR feels too close to the implementation details | `Use $claude-from-codex to review README.md as a first-time Codex user. Flag anything that sounds like internal planning instead of user-facing docs.` |
| `pnpm test` fails and Codex is already working on a fix | `Use $claude-from-codex to investigate the failing pnpm test output in parallel. Do not edit files; return the likely root cause and the smallest fix.` |
| You have an implementation plan but want a simpler alternative | `Use $claude-from-codex to critique docs/plans/2026-06-17-001-feat-claude-from-codex-skill-plan.md. Look for overengineering, missing tests, and a smaller path.` |
| You explicitly want Claude to make a narrow edit | `Use $claude-from-codex to add a regression test for the XDG_STATE_HOME background-job case. Keep the change scoped, then show me the diff before continuing.` |
More copy-paste prompts are in [docs/examples.md](docs/examples.md).
## Install
### Ask Codex To Install It
If you want a dedicated install prompt, paste this into your current agent:
```text
Install the Codex skill from https://github.com/yujingz/use-claude-code-from-codex.
Prefer the vercel-labs/skills installer if it is available.
Install the skill named claude-from-codex for Codex, then verify that $claude-from-codex is discoverable.
```
### Install From Terminal
If you prefer a terminal command, use [`vercel-labs/skills`](https://github.com/vercel-labs/skills):
```sh
npx skills add yujingz/use-claude-code-from-codex --skill claude-from-codex -g -a codex -y
```
This installs the skill globally for Codex.
### Manual Install
If you do not want to use `npx skills`, download or clone this repo and link the skill folder yourself:
```sh
git clone https://github.com/yujingz/use-claude-code-from-codex.git
cd use-claude-code-from-codex
mkdir -p "$HOME/.agents/skills"
ln -s "$PWD/skills/claude-from-codex" "$HOME/.agents/skills/claude-from-codex"
```
If your Codex setup uses a different skills directory, link the same `skills/claude-from-codex` folder there instead.
### Verify Discovery
Restart Codex or start a new Codex session, then check that `$claude-from-codex` appears in the available skills.
If you installed from a terminal, these local checks can help:
```sh
npx skills list -g -a codex
codex debug prompt-input '$claude-from-codex discovery check; do not run commands' | rg 'claude-from-codex'
```
## Basic Usage
After installation, just ask Codex to use the skill. You do not need to run Claude commands yourself.
Treat Claude's answer as one review signal, not ground truth. Keep checking files, tests, and diffs before acting on Claude's advice.
For write-capable work, say that explicitly:
```text
Use $claude-from-codex to let Claude make a small implementation pass on this bug.
Keep the change scoped to the failing test, then show me the diff before we continue.
```
## Troubleshooting
If Claude works in your normal terminal but not inside Codex, ask Codex:
```text
Use $claude-from-codex to check whether Codex can see my local Claude Code CLI.
Report what is missing.
```
Common causes:
- `claude` is not on the PATH visible to Codex.
- Codex was launched from an environment that cannot see the same tools as your terminal.
Advanced diagnostics and background job commands are documented in [docs/companion-cli.md](docs/companion-cli.md).
## Development
Run the test suite with pnpm:
```sh
pnpm test
```
The tests use a fake Claude executable. They do not call the real Claude API.