Live data from Hacker News

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

medium.com

21–30 of 95 posts

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

#21

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.

It's hard enough to get the same model to be consistent around it's vision let alone multiple of them.

I'm building an EMR and the other day asked Claude what a decent model would look like for capturing wound orders. Then, I took the output, started a new session and asked the new session to critique that model and the response made me want to pull my hair out. It blasted the model from it's former self and suggested making a ton of updates.

I'm sure more scoped tasks would fair better, but it was pretty frustrating.

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

#22

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

Does it not turn into a never-ending snowball? Do they eventually agree on something?

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

#24

I let them talk via tmux, two panes, each has an agent and agents know how to send text via tmux to panes.

This. I built a wrapper Tmux-cli to make this more reliable:

https://pchalasani.github.io/claude-code-tools/tools/tmux-cl...

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

#25

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

Agree that the intermediary is not very useful when you can just use a directory watcher, but driving Claude via another app incurs api level costs starting this month, according to the new ToS.

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

#27
post #13

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.

There was the commercial of a bank using mobile banking as a chat system by sending 1ct back and forth and using the description.

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

#28

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.

or via humans communicating via slack. happeneing all over workplaces.

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

#29

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

I vastly prefer Beans, https://github.com/hmans/beans, for much simpler code and use.

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

#30

I let them talk via tmux, two panes, each has an agent and agents know how to send text via tmux to panes.

This. I built a wrapper Tmux-cli to make this more reliable: https://pchalasani.github.io/claude-code-tools/tools/tmux-cl...

can this be used to launch subagents in tmux
Post reply on HN