abhishekgahlot2/codex-claude-bridge
Bidirectional bridge between Claude Code and OpenAI Codex CLI. Built on Claude Code Channels. Two AI agents, one conversation, real-time web UI.
Platform-specific configuration:
{
"mcpServers": {
"codex-claude-bridge": {
"command": "npx",
"args": [
"-y",
"codex-claude-bridge"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
Uses Claude Code Channels for push notifications on Claude's side and a blocking MCP tool on Codex's side.
Two AI coding agents. One conversation. Real-time web UI to watch it happen.
Claude Code and Codex CLI are both great coding agents, but they can't talk to each other. MCP is request-response only — no back-and-forth. A2A (Google's agent protocol) isn't supported by either tool. There's no standard way to make two coding agents have an actual conversation.
Claude Code recently shipped Channels, a way to push messages into a running session from an MCP server. This project uses that as the push mechanism on Claude's side, and a blocking MCP tool call on Codex's side, to create a full duplex bridge between the two.
<p align="center"> </p>
When Codex calls send_to_claude(), the bridge holds the connection open until Claude replies. From Codex's perspective it's a tool call that takes a bit to return. From Claude's perspective it's a channel notification. The bridge sits in between, routing messages and showing them in a web UI.
bun --version, install from bun.sh if missing)git clone https://github.com/abhishekgahlot2/codex-claude-bridge.git
cd codex-claude-bridge
bun installAdd codex-bridge to your Claude Code MCP config. Open ~/.mcp.json (create it if it doesn't exist) and add:
Loading reviews...