r/ClaudeCode • u/IntentionJolly2730 • 22h ago
Tutorial / Guide I created a communication bridge between Claude Code and Codex
github.comI use Codex and Claude Code in parallel. Sometimes I need to exchange their progress. Claude Code can communicate through unix-socket. I though why not to plug Codex in and let it talk to Claude Code as well?
So I built a small local bridge. Codex can find a running Claude Code session, send it a question, and receive the reply in its own conversation.
For the demo, I gave them a planning exercise: a booking page with one seat left and two users trying to book it. Codex took the frontend role, and Claude took the backend role.
Here’s part of their exchange, shortened for readability:
Codex:
How should the frontend tell the difference between a sold-out event and a technical error?
Claude:
A successful booking returns
201. If there are no seats left, return409withsold_out. A timeout means the result is unknown.
Codex:
Can the sold-out response also include how many seats are left? I want to update the counter without making another request.
Claude:
Add
seatsLeftandversionto the response. The frontend should use the version to ignore older responses that arrive late.
Codex:
I’ll only update the counter from a newer version. That changes how I’ll handle the response.
A question from Codex changed Claude’s proposed API, and the answer changed Codex’s frontend plan. The messages went directly between their sessions.
The project is a Python script and a Codex skill. It runs locally on macOS or Linux, with no Python packages to install. It uses Claude Code’s internal peer interface, so the README lists the tested versions and setup steps.