Compared

Murmell vs Replit Agent

Replit Agent turns a description into a working application and puts it on the internet. Murmell runs real coding agents on a repository you already have, several of them at once, in one directory.

The real difference

Replit owns the whole road. It says Agent “writes code, sets up infrastructure, and tests the result”, needs no technical knowledge from you, keeps checkpoints you can roll back to, and takes the app all the way to deployment. The agent is the interface, and the terminal is an implementation detail you are not asked to look at.

Murmell is the opposite arrangement. The terminal is the point. You open Claude Code or Codex in a window, you read what it actually printed, and you open a second one beside it in the same checkout. An agent claims a path before it writes, the board keeps one holder per path and refuses everyone else until it is released, and a colliding write is snapshotted before it lands. Murmell does not host anything: work goes to a private repository for the project.

Where Replit wins

Two things, and both are large. It gets you from a sentence to a URL without leaving the tab, with the database and the hosting handled, and Murmell has none of that.

And its multiplayer is older and wider than ours. Replit documents that several people can work in the same project at the same time with cursor presence, and each of them can start their own thread with Agent. Murmell shows guests the canvas live, with a name and a colour on each cursor, but two people typing raw keys into the same terminal is not built yet. If a colleague needs to take the keyboard from you in the same shell today, Replit does that and Murmell does not.

Which to pick

Pick Replit when the app does not exist yet and you want it running by this evening, or when the people building it would rather not think about infrastructure.

Pick Murmell when the codebase is already real, the change is bigger than one agent, and you want to watch the run. Read links cost nothing and are not capped, edit links are capped by plan, and the machine that executes agent code holds no database and no decryption key. See what the canvas is.