Compared

Murmell vs GitHub Copilot and Agent HQ

Agent HQ is GitHub turning its own primitives into an agent platform. You assign work from mission control, agents go away and come back as pull requests. Murmell is a canvas of live terminals where several agents share one directory and you watch them do it.

The real difference

GitHub is explicit about the unit of work. The Copilot coding agent has “its own ephemeral development environment, powered by GitHub Actions”, it “can only work on one branch at a time”, and it “can open exactly one pull request to address each task it is assigned”. Mission control then lets you “choose from a fleet of agents, assign them work in parallel, and track their progress from any device”. Parallel means many branches at once, and everything converges at review.

Murmell converges earlier. Agents work in one checkout on one cloud machine and claim a path before writing to it, so the collision is settled while it is still a question of whose turn it is rather than a question of which diff survives. A colliding write is snapshotted before it lands.

The other gap is the watching. Agent HQ tracks progress; Murmell shows the terminal. Send a read link and someone sees the actual output scrolling, which window each person is looking at, and a named cursor for each of them.

Where Agent HQ wins

It is already where your code lives. Branch controls, rulesets, required checks, identity and org policy all apply to agents the same way they apply to people, and nobody has to configure a second place for any of it. GitHub puts it as “agents and developers building together, on the infrastructure you already trust”, and that is a genuine advantage that no separate product can copy.

It also lets you bring several vendors’ agents into one interface, give them a persona from a file in the repository, and run them on your own runners. If your governance story has to be one story, Agent HQ is that story.

Which to pick

Pick Copilot and Agent HQ for work that decomposes into issues, where the review process is the product and each agent can be left alone on a branch until it is done.

Pick Murmell for the hour where several agents have to move through the same files together, or where a colleague needs to be looking at the run with you. It sits before the pull request rather than instead of it. See what the canvas is.