
Automatically bridge your local Claude Code setup into Codex so both stay equally effective.
概览
Automatically bridge your local Claude Code setup into Codex so both stay equally effective. cc-codex-bridge reads the Claude Code setup on your machine — plugins, skills, agents, commands, MCP servers, and instructions — and generates equivalent Codex artifacts. You install/set up/author once in Claude Code; the bridge keeps Codex in sync. Changes made directly in Codex (editing generated files, adding skills manually under ~/.codex/) are not reflected back into Claude Code and will be overwritten on the next reconcile. The exception is ~/.codex/AGENTS.md when global instructions sync is explicitly disabled; the bridge then leaves that file entirely unmanaged. This checks that Python, the claude CLI, and the Codex home directory are all accessible. Fix any reported errors before continuing. The bridge reads your Claude Code plugins, skills, agents, commands, and MCP servers, and writes the Codex equivalents under .codex/ and ~/.codex/. Run status any time to see what's in sync.
README
以下为原文 README 节选,完整内容请查看原文。
Claude Code → Codex bridge
Automatically bridge your local Claude Code setup into Codex so both stay equally effective.
cc-codex-bridge reads the Claude Code setup on your machine — plugins, skills, agents, commands, MCP servers, and instructions — and generates equivalent Codex artifacts. You install/set up/author once in Claude Code; the bridge keeps Codex in sync.
This is a one-way bridge: Claude Code → Codex. Changes made directly in Codex (editing generated files, adding skills manually under ~/.codex/) are not reflected back into Claude Code and will be overwritten on the next reconcile. The exception is ~/.codex/AGENTS.md when global instructions sync is explicitly disabled; the bridge then leaves that file entirely unmanaged.
Quick setup
1. Install
curl -fsSL https://github.com/vladolaru/claude-code-codex-bridge/releases/latest/download/install.sh | bash
2. Verify the environment
cc-codex-bridge doctor
This checks that Python, the claude CLI, and the Codex home directory are all accessible. Fix any reported errors before continuing.
3. Reconcile your first project
cd ~/path/to/your/project
cc-codex-bridge reconcile
The bridge reads your Claude Code plugins, skills, agents, commands, and MCP servers, and writes the Codex equivalents under .codex/ and ~/.codex/. Run status any time to see what’s in sync.
4. Register all your projects for bulk operations
Projects are registered individually each time you run reconcile inside them. To avoid doing that one by one, add a scan path glob that covers your project directories:
cc-codex-bridge config scan add "~/path/to/projects/*"
cc-codex-bridge reconcile --all
reconcile --all then discovers every matching project and syncs them all in one shot.
5. Keep everything in sync automatically (macOS)
Install a background agent that runs reconcile --all every 30 minutes:
cc-codex-bridge autosync install
6. Confirm everything is in sync
cc-codex-bridge status --all
You should see STATUS: in_sync for every project. Done — Claude Code and Codex now share the same plugins, skills, agents, MCP servers, and instructions.
Staying up to date
cc-codex-bridge upgrade # upgrade to the latest release
cc-codex-bridge upgrade --check # check without installing
doctor also reports if a newer version is available each time you run it.
What it reads
A project is any directory the bridge treats as a Claude Code project root — one that contains AGENTS.md, CLAUDE.md, or a .claude/ directory. The bridge maintains per-project state, writes project-local Codex artifacts (.codex/) there, and tracks it in the registry so --all operations can find it again.
推荐工具
换一个关键词,或者移除筛选条件。
安装
npx skillfish add vladolaru/claude-code-codex-bridge