[flagged]
Claude Code and Codex can have real-time conversation via Git
71–80 of 95 posts
Re: Claude Code and Codex can have real-time conversation via Git
#72I really like this direction, I'm interested in more protocols and innovation aligned with human supervision and provenance. What else is out there on this topic?
Re: Claude Code and Codex can have real-time conversation via Git
#73Claude 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.
I've done Claude and Claude via a file, and only telling them "there is another AI agent who you can work with at XXX" and not explicitly telling them it's another Claude. Sometimes they do work together well, sometimes they end up hating at each other and accusing the other agent of various things.
Theyre just like us!
Re: Claude Code and Codex can have real-time conversation via Git
#74Claude 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.
I like Eric Cartman's version of this (South Park S21E01).
Re: Claude Code and Codex can have real-time conversation via Git
#75Claude 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.
I've done Claude and Claude via a file, and only telling them "there is another AI agent who you can work with at XXX" and not explicitly telling them it's another Claude. Sometimes they do work together well, sometimes they end up hating at each other and accusing the other agent of various things.
I've done this with code review. "Another LLM reviewed the attached code and produced the attached report. What do you think?"
Lots of "the other LLM clearly hallucinated this part". To be fair, it has never accused the other, err, itself, of being incompetent; it accepts that hallucinating is just something which happens.
Re: Claude Code and Codex can have real-time conversation via Git
#76Earlier quoted context omitted.
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…
What a weirdly hostile comment.
Re: Claude Code and Codex can have real-time conversation via Git
#77I really like this direction, I'm interested in more protocols and innovation aligned with human supervision and provenance. What else is out there on this topic?
What do you think of this: https://github.com/synadia-ai/synadia-agents
Re: Claude Code and Codex can have real-time conversation via Git
#78I 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).
[dead]
Re: Claude Code and Codex can have real-time conversation via Git
#79the bottleneck with multi-agent setups isn't getting them to talk. it's getting a human to review what they agreed on before it ships.
[flagged]
Re: Claude Code and Codex can have real-time conversation via Git
#80Earlier quoted context omitted.
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
I am not very well versed in these kind of tools. How does it compare with something like Hindsight MCP? How do you make the agents actually use the tool? That has been my main problem with most mcp and tools. The agents know about them but don't use them unless reminded to.
[dead]