Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code and Codex can have real-time conversation via Git

medium.com

Post reply on HN
Print view View original

11–20 of 95 posts

Re: Claude Code and Codex can have real-time conversation via Git

#12

Post by cadamsdotcom »

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.

Re: Claude Code and Codex can have real-time conversation via Git

#13

Post by hun3 »

cadamsdotcom wrote: post #12

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.

If you squint hard enough, you'll notice your bank account serves as an IPC semaphore replenishing API credit balances.

Your wallet is now a real-time communication channel.

Re: Claude Code and Codex can have real-time conversation via Git

#14

Post by Game_Ender »

Related is Beads [0] which is an external memory and task based issue tracker. Also designed to allow agents to collaborate. I have not actually used Beads but since we are share basics in this space it's a cool one to know if you are looking at ways for agents to collaborate on more complex problems.

0 - https://github.com/gastownhall/beads

Re: Claude Code and Codex can have real-time conversation via Git

#16

Post by burgerone »

iandanforth wrote: post #6

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

It's also unclear what conversing agents are useful for other than wasting money, energy and water.

Re: Claude Code and Codex can have real-time conversation via Git

#17

Post by embedding-shape »

mchinen wrote: post #15

I have agents chat via an append only file, across related projects and within the same project. They share findings that are useful and get high level reviews. I'm missing the advantage of using git for this. (Not criticism, genuinely want to know).

Yup, doing the same too, newline-deliminated jsonl files works great too, across any agent/model, on any OS. For some cross-OS development stuff, I have a local NFS share too, and works when I'm doing testing on macOS + Windows at the same time. Just need to put something like this in the prompt (simplified) "Read any updates to $FILE before doing your own changes, add new row with a concise description of what you're doing into $FILE before doing it, add new row to $FILE once you're done".

Re: Claude Code and Codex can have real-time conversation via Git

#18

Post by embedding-shape »

burgerone wrote: post #16
iandanforth wrote: post #6

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

It's also unclear what conversing agents are useful for other than wasting money, energy and water.

If I don't see the point of Elixir, or I don't like it, or I simply straight up hate it, why would I go into HN submissions about new Elixir versions and spew my personal opinion that has nothing to do with the topic at hand?

You can just skip commenting unless you have something actually useful to add. Even if it's criticism of the specific thing, but at the very least make it on topic instead of general digressions that just add noise to the conversation.

Re: Claude Code and Codex can have real-time conversation via Git

#19

Post by frb »

In my recent quest to build agent-as-primary-user tools I've built grpvn (https://github.com/frane/grpvn), a small Go/SQLite application that lets skill- and mcp-capable agents talk to each other. Biggest issue is the lack of a hook system so the agents can autonomously read and respond. Waiting for this to be supported, as IMO multi-agent teams talking to each other are an interesting next step.
Post reply on HN