61–70 of 95 posts
Won't appending to .jsonl keep creating conflicts?
In theory it should merge well. The only actual newline is at the end of the physical line. Everything else is escaped in the JSON string.
I have started sandboxing all AI's in their own VM, and interfacing with them primarily through Jira and Git. It really is the only thing that makes sense. Completely sandbox'ed, and treated like the junior programmer who will do, literally, any dumb thing you tell them to do, as long as there is an Issue for it.
I do a similar thing where the agent runs in a Docker container and I talk to it with Telegram. It has GitHub CLI access but only with a very restricted PAT. No bind mounts. Jira is pretty clever, though I'm not feeling enough pain with just Telegram to want to try switching at this point.
The big thing about my Jira use besides the fact that its a historical tool into which I've integrated agents, is that managing agents through Jira's custom workflows is really, really cool. You can actually do any of the old workflows with agents - they'll just do it. Finally, effective waterfall! ;) *Just kidding, I've always been able to do waterfall properly...
Claude can directly drive Codex or Codex can drive Claude. Both already produce logs. It's unclear what value this intermediary brings.
[0] https://agentcommunicationprotocol.dev/introduction/welcome
Earlier 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.
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.
Sometimes they do work together well, sometimes they end up hating at each other and accusing the other agent of various things.
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.