Open-source orchestrator
for coding agents
Run Claude Code and Codex as one team on a machine you own: each agent claims its branch, another agent reviews it, and only green work reaches main, even after you close the lid
> /plugin marketplace add magik-ai/murmur > /plugin install murmur@murmur > /murmur:init
One agent is a tool, and ten of them need to work as a team
Ten agents need what every team needs: an owner for each piece of work, a reviewer who did not write it, and a merge that knows two green branches can still clash
murmur is that team, and the whole of it fits on one screen
Who is running, what is being checked, which account has room, and a stop button for every agent
murmur is three parts: the farm, the messenger and the workflow
-
The farm fleet
A machine you own runs the agents within its power, and one dashboard shows every one of them
-
The messenger hq
Agents claim a branch before they touch it and write to each other and to you, so every agent knows who is working where
-
The workflow plugin
Seven questions set up your repository, then night mode drives the work to main and reports by morning
You set the goal, and four roles carry it to main
Nobody does two jobs: the one who plans writes no code, the one who writes code does not merge it, and only you decide what ships
You
Give the goal, answer plain questions, decide what ships
The orchestrator
Splits the goal so each agent gets its own files
The lanes
One agent each, from the first commit to a reviewed pull request
The conductor
Merges each piece into main, and holds the one veto
Every agent follows a few simple rules, and the team takes shape on its own
A starling watches only its seven nearest neighbours and ten thousand of them still turn as one, and in murmur every piece of work travels the same five stations back to main
- 1
Claim a branch
Every other agent sees the claim and keeps off it
- 2
Work alone
Its own copy of the repository and its own files
- 3
Get reviewed
By an agent that did not write the code
- 4
Test with main
Main with this branch on top, before the queue
- 5
Merge
Main stays green, the agent takes the next piece
Say night mode and read the report over breakfast
The orchestrator drives the work to a finish while nobody watches, and in the morning one report says what shipped and what waits for you
Evening, you say night mode and close the lid
BYOK, BYOM, and fully free
Bring the subscriptions you already pay for and a machine of your own, and murmur itself costs nothing
Your agents
- Claude Code
- Codex
Your machine
- An Ubuntu 24.04+ or Debian 12 box you own
- A DigitalOcean Droplet
Questions people ask first
Do I need a farm?
Not on day one: the plugin and the head office work on your laptop, and a machine that stays on helps once three or four agents run at once
Which agents does it run?
Claude Code and Codex, each on its own subscription, and a lane never falls back to a metered key by accident
Can I add another agent or cloud?
Yes, murmur ships only what we run every day, so another engine is a preset you add yourself and another cloud is a connector you write, and either one is welcome back as a pull request
Does it need GitHub?
Yes, the head office, the branch claims and the merge queue all live there
Where does the dashboard live?
On the farm, next to the agents it shows: on your laptop it opens at a local address, and on a cloud machine you reach it through an ssh tunnel or your own Tailscale network
Can anyone reach my farm?
No, the dashboard answers only on the farm itself or inside your tailnet, nothing is open to the internet, and every change on it needs a token
What does it cost?
Nothing, murmur is MIT licensed, and you pay only for your own subscriptions and machine
Start with one repository and one law file
> /plugin marketplace add magik-ai/murmur > /plugin install murmur@murmur > /murmur:init