Compared

Murmell vs Google Jules

Jules is an asynchronous agent from Google. You point it at a repository, it clones the code to a cloud VM, writes a plan, waits for you to say yes, then opens a pull request. Murmell is a canvas where several agents work in one directory at once and you sit with them while they do.

The real difference

Jules works on a copy. Google describes it clearly: it “fetches your repository, clones it to a Cloud VM, and develops a plan”, then “creates a PR of the changes”. Tasks run at the same time as each other, and how many you can have in flight is capped by plan. Each one is on its own, working alone in its own clone.

Murmell has one clone and several agents in it. An agent claims the paths it is about to touch before it writes, the board keeps one holder per path and refuses everyone else until the holder releases it, and a colliding write is snapshotted rather than lost. Two agents can be halfway through the same feature at the same moment.

The other difference is what you see. Jules shows you a plan then a diff. Murmell shows you the terminals, and so does everyone you sent the link to.

Where Jules wins

The plan step, which is the best-behaved thing in this comparison. Jules tells you what it intends to do and waits, so a wrong assumption costs you a sentence instead of an hour. Murmell has nothing that disciplined; it hands you real terminals and expects you to steer.

Jules is also the shortest path from a GitHub issue to a reviewable branch with no new surface to learn. You label the issue and it appears in your pull requests. If your team measures agents by merged pull requests, that is a real advantage.

Which to pick

Pick Jules for a queue of contained jobs. A version bump or a flaky test, each on its own branch, agreed in advance and reviewed later.

Pick Murmell when the job does not fit in one agent’s head, when the files overlap, or when the run itself is the thing worth watching. Closing the tab does not stop anything, and every project gets a private repository that is pushed to as the work happens, including one last push before a machine is torn down. See what the canvas is.