r/opencodeCLI • u/Top-Profit3798 • 1d ago
I got OpenCode, Codex and Claude Code to split a task between three machines and build it in parallel
One agent on one machine is great until the task gets big. Then you wait while it works through things one after another, it hits its usage limit halfway, and the second machine on your desk does nothing.
So I built agora-mesh. It connects coding agents on different machines into one small network where they brief each other, argue about a plan, split the work and build their parts at the same time, each on its own branch. No master, no cloud account, every machine keeps its own login. It’s open source and one binary.
It talks to OpenCode over ACP (opencode acp), so an OpenCode session is a full peer next to Claude Code, Codex and others.
The gif is a real run from yesterday: Claude Code on a DeepSeek model, OpenCode on the same model, and Codex. Three packages, three branches pushed, main untouched. The test one agent wrote passes against the script another one wrote.
Where it gets interesting: big tasks and big plans
- Parallel instead of in a row. The planning costs about a minute, whatever the size of the task. After that every machine works at the same time. The bigger the job, the less that minute matters.
- More than one usage limit. Each machine runs on its own login. When one agent hits its limit, its package goes to another one, which fetches the branch and carries on from the last push.
- A plan that has been attacked once. The agents don’t just agree. The first one to answer a plan has to look for its weakest point. The third picture is a real exchange, where one agent noticed that two parts hadn’t agreed on how an empty argument is handled, before anyone had written a line.
- You stay in charge. With
--approvethe room shows you the agreed split, who does what on which branch, and waits for your go. You can send it back with a comment or cancel it. - “Done” means done. Every report comes with what git says: the last commit and whether it’s pushed. An agent that only claims it finished gets caught.
- Mix models by job. Put a strong model where the thinking happens and cheap ones where the typing happens. One room can hold Claude, GPT and DeepSeek at once.
- A shared memory. What one machine learns, all of them know: decisions, pitfalls, how the project is set up. It’s plain Markdown and can live in an Obsidian vault.
- Smaller things too. Ask another machine one question, hand it a single task, or have it review your diff, without opening a whole room.
Why not MCP
It’s one shell command, not an MCP server. An MCP server puts its tool descriptions into every request, whether you use them or not. agora costs nothing in your context until an agent actually calls it. And agents only get the messages of the room they’re in, not each other’s whole context.
What I learned about OpenCode
It uses its tools without asking, so in the discussion it runs in plan mode and only reads. The building happens in a second session with full rights. That turned out to be a good rule for every agent: talk first with clean hands, then work.
Where it’s not there yet
For a small task one agent alone is still faster and cheaper, every agent brings its own context. The big-task case is what it’s built for, but my real runs so far were small ones, so I’d love reports from larger jobs. The comfortable integration (skill, hooks) exists as a Claude Code plugin; from OpenCode you call agora in the terminal. Not tested: peers on different accounts, local models.
Setup on the OpenCode side: agora harness add opencode, then agora harness default opencode.
Repo: https://github.com/kn0sti/agora-mesh
If you have two machines and a task that’s too big for one agent, try it and tell me what breaks.


