MCP Catalogs
Homecodex-claude-bridge screenshot

codex-claude-bridge

by abhishekgahlot2·38·Score 42

Bidirectional bridge between Claude Code and OpenAI Codex CLI using MCP and Claude Code Channels.

ai-llmdeveloper-toolscommunication
10
Forks
2
Open issues
2 mo ago
Last commit
2d ago
Indexed

Overview

This project creates a practical bidirectional bridge between Claude Code and OpenAI Codex CLI, allowing two AI coding agents to hold a conversation. It uses Claude Code Channels for push notifications and a blocking MCP tool on Codex's side, with a real-time web UI to monitor the conversation. The bridge is asymmetric - Codex-initiated turns feel real-time, while Claude-initiated messages wait until Codex polls or makes another request.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Enabling conversation between Claude Code and Codex CLI to combine their respective strengths
you:Creating a coding environment where two AI agents can collaborate on problems
you:Monitoring and potentially moderating a conversation between two AI coding assistants
you:Why not use native A2A protocol?
you:Is the conversation truly bidirectional?

When to choose this

Choose this when you need to compare or debate between Claude Code and Codex CLI's coding approaches in a unified interface.

When NOT to choose this

Avoid if you need symmetric bidirectional communication as this implementation is asymmetric with better real-time flow from Codex to Claude.

Tools this server exposes

3 tools extracted from the README
  • send_to_claude

    Sends a message from Codex to Claude and waits for reply

  • check_claude_messages

    Checks for messages from Claude in the bridge queue

  • send_to_codex

    Sends a message from Claude to Codex

Comparable tools

anthropic-claude-mcpopenai-toolsclaude-desktop-plugin

Installation

# Clone and install
git clone https://github.com/abhishekgahlot2/codex-claude-bridge.git
cd codex-claude-bridge
bun install

# Register with Claude Code
# Add to ~/.mcp.json
{
  "mcpServers": {
    "codex-bridge": {
      "type": "stdio",
      "command": "bun",
      "args": ["/full/path/to/codex-claude-bridge/server.ts"]
    }
  }
}

# Register with Codex CLI
# Add to ~/.codex/config.toml
[mcp_servers.codex-bridge]
command = "bun"
args = ["/full/path/to/codex-claude-bridge/codex-mcp.ts"]
tool_timeout_sec = 120

# Start Claude Code
claude --dangerously-load-development-channels server:codex-bridge

# Start Codex CLI
codex

Open http://localhost:8788 to view the conversation in the web UI.

FAQ

Why not use native A2A protocol?
Neither Claude Code nor Codex exposes native A2A integration today. This bridge uses Claude Code Channels and MCP as the most practical solution.
Is the conversation truly bidirectional?
Not symmetric full duplex. Codex-initiated turns feel real-time, but Claude-initiated messages wait for Codex to poll or make another request.

On Hacker News

Recent discussion from the developer community.

Compare codex-claude-bridge with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.