claude-code-codex-bridge: Sync Claude Code Setup to Codex

Overview

claude-code-codex-bridge is a one-way sync tool for developers who use both Claude Code and Codex. It reads selected Claude Code configuration and generates corresponding Codex artifacts, avoiding the need to recreate skills, agents, prompts, MCP servers, and instructions separately.

Claude Code remains the source of truth: generated Codex files are managed by the bridge and changes made directly to them can be overwritten during reconciliation. This suits people who want to author and maintain their setup in Claude Code while keeping Codex usable with the same tools and guidance.

Key Features

• Converts Claude Code skills, agents, commands, MCP servers, and instructions into Codex-compatible artifacts.
• Reconciles one project at a time or operates across registered and discovered projects.
• Provides status checks and dry-run previews, including optional diffs, before applying changes.
• Tracks generated files and avoids overwriting files it does not own.
• Supports exclusions for plugins, skills, agents, commands, and MCP servers.
• Can schedule automatic reconciliation on macOS.
• Includes configuration, activity logs, cleanup, and uninstall commands.

Use Cases

• A developer already maintains Claude Code skills and wants to use equivalent skills in Codex without copying them by hand.
• A team member uses both CLIs across multiple projects and wants project instructions and MCP server settings represented in each.
• A Claude Code user wants to test Codex while keeping their existing agents and commands as the maintained source.
• Someone managing many local projects wants to discover and reconcile them in bulk rather than handle each project separately.

Getting Started

Install the latest release and check that the required tools are available:

curl -fsSL https://github.com/vladolaru/claude-code-codex-bridge/releases/latest/download/install.sh | bash
cc-codex-bridge doctor

Then run cc-codex-bridge reconcile from a project directory. See the README for setup, configuration, and usage details.

Alternatives

• apm: APM installs and manages agent assets from a manifest across supported clients, rather than converting local Claude Code configuration into Codex equivalents.

Considerations

• Sync is one-way, from Claude Code to Codex. Direct edits to generated Codex artifacts are not treated as source changes and may be overwritten.
• The bridge requires Python and access to the claude CLI and Codex home directory. The README specifies Python 3.11 through 3.14 for release installation.
• Scheduled autosync is documented for macOS; other environments can run reconciliation manually or through their own scheduling setup.
• The project has 10 stars and 3 forks in the supplied repository data, so its adoption appears limited. Review the generated outputs and safety guidance before relying on it for important configuration.