Claude Code and Codex Can Have Real-Time Conversation via Git

▲ Claude Code and Codex Can Have Real-Time Conversation via Git(medium.com)

21 points by syumei 4 days ago | 10 comments

▲ cadamsdotcom 9 minutes ago | parent | next [-]

Claude and Codex can have real time conversation via a git repo, or via a file, via a Unix socket, via the terminal, via a human, via two humans shouting back and forth over a comically high office partition, or entirely by setting up chess board states only reachable after both sides have castled.

	▲	hun3 5 minutes ago \| parent [-]
		[delayed]

▲ iandanforth 39 minutes ago | parent | prev | next [-]

Claude can directly drive Codex or Codex can drive Claude. Both already produce logs. It's unclear what value this intermediary brings.

▲ FlippieFinance 4 days ago | parent | prev | next [-]

This is actually so great. I mainly use Claude Code but sometimes I am sending over a message to Codex asking what he thinks of the idea of Claude Code. This can save so much time :D

▲

rcarmo 25 minutes ago | parent | next [-]

I added a chat tool to https://github.com/rcarmo/piclaw, so any active session can chat to each other, regardless of what model they run. It's led to interesting outcomes: https://x.com/rcarmo/status/2054185558402904338?s=20

▲

fjwood69 4 days ago | parent | prev [-]

So I solved this by using NATS and letting each agent pub / sub to the shared message bus.. simple binary you can run anywhere and it's highly useful! Part of a broader tool I created - https://github.com/fjwood69/mori

▲

FlippieFinance 4 days ago | parent [-]

thanks for sharing dude. How long did this take you?

	▲	fjwood69 4 days ago \| parent [-]
		about six weeks.. Pushed a v1.0 product with a huge list of v2.x enhancements and features inbound. to your point about asking Codex.. that's my /consult feature. spin out the current context in any number of ways to ask for advice.. on a plan, on a specific architectural decision, on a security basis.. I use it all the time as a check on everything Claude Code proposes. any / all feedback most welcome. fw

▲ stuaxo 36 minutes ago | parent | prev | next [-]

This is interesting, it would be good to show an session.

▲ mettamage 33 minutes ago | parent | prev [-]

> Claude Code and Codex to collaborate as if they were having a real-time conversation

How is this new? I vibe coded something in a similar vein months ago. In my case they send markdown files to each other and have a watcher that watches the folders of all the other agents.

If this type of stuff is frontpage news, let me share what I cobbled together.

  ls ~/.agent/projects/<my_project>/callgraph

  callgraph.current.md         callgraph.last.read.agent.md
  callgraph.diff.md

The current callgraph is a callgraph only of my own defined functions that agents can read. It shows certain software design issues fairly quickly. callgraph.diff.md is to send the diff through. I have a vibecoded script that agents can use to create the callgraph. It works for my projects.

  ls ~/.agent/projects/<my_project>/memo
  architect   coder  retro     tester

retro is not a role, it's just a handover folder. The other 3 are roles that agents can use and then they need to make a folder with their name. For example:

  ls ~/.agent/projects/<my_project>/memo/architect
  1_Daedalus     3_Brunelleschi 5_Wren         7_Sinan
  2_Vitruvius    4_Imhotep      6_Hadid        8_Palladio

  ls ~/.agent/projects/<my_project>/memo/architect/7_Sinan
  20260507___1802_to_Hadid.md    20260507___2035_to_Quench.md
  20260507___1959_to_Crucible.md 20260511___1401_to_Quench.md
  20260507___2008_to_Quench.md   20260511___1403_to_Quench.md
  20260507___2030_to_Quench.md   read.md

read.md is the index that an agent keeps track of so it knows what it doesn't need to read. The .md files are memo's that it sends to other agents. The other agents are being told to see if an agent writes anything in its own folder (so they check all the folders except their own) and are able to detect to see if they need to read something.

  ls ~/.agent/projects/<my_project>/memo/coder
  10_Mallet   12_Crucible 14_Swage    2_Forge     4_Anvil     6_Tongs     8_Chisel
  11_Auger    13_Quench   1_Atlas     3_Rivet     5_Bellows   7_Hammer    9_Vise

As you can see, Sinan sent most of its message to Quench, a coder.

This is because architects read a very comprehensive guide on software design/architecture and get to use the callgraph utility but cannot see the code. Coders read the codebase in full but only read a small markdown file on how to write readable code. And of course, every agent that is set up this way have to read a markdown file on how to use the memo system.

If I'd need a memo system like this for like 25 agents, I'd need something different but up until 5 agent with me looking at 5 terminal windows worked well enough.