[mschwarz]

Thanks! It doesn't use A2A but that might be a good roadmap item, there's a ton of overlap with it. OpenRig already has a lot of A2A like wiring built-in but simpler and intentionally stripped down to keep things inspectable by a single human operator trying to manage a fleet of agents. It just uses TMUX for agent-to-agent messaging- super simple but effective. For tasks, handoffs, etc there is a custom event stream and queue system.

[NBenkovich]

Got it! But what do you think about isolation of agents? If you use tmux, each agent has the same network, filesystem and etc

[mschwarz]

Yeah so right now OpenRig isn't trying to solve that problem yet, but thats a very interesting direction to take it someday. It currently assumes you the operator are running coding agents on a host you control, like your mac or a VPS, and you actually want all the agents to have access to the same network and file system, so they can work together without friction. It basically takes the core single-user UX of CLI coding agents like claude code and asks the question "what if i could scale this up and run 10, 50, 100 of these things in parallel." OpenRig is the result of the last 9 months of exploring that branch of the AI tree very heavily.

[NBenkovich]

Got it! Thanks for answering!