Explained
Multiplayer coding with AI agents
Multiplayer on Murmell means two things at once. Several coding agents work in one project directory on a cloud machine, and several people watch and steer that canvas from their own browsers, each cursor carrying a name.
It is one URL. Nobody installs anything, nobody takes a copy, and nobody has to be screen sharing for the others to see the work happen.
What a guest sees
You send a link. Whoever opens it gets the canvas as it stands, not a recording. They see the windows where they are and the terminal output arriving line by line. They see the other cursors move, with a name on each, and which window each person is watching.
Read links are free and there is no limit on how many you give out. Links that let somebody drive an agent are capped by your plan, which is the honest shape of it: looking costs us almost nothing, and a machine costs what a machine costs.
What each person can do
Each person drives their own agents, and everyone sees all of them. That is a different shape from two hands on one object: the shared thing is the canvas and the directory under it, not a single keyboard.
It is enough for the thing people actually do together, which is deciding what the agents should be doing. You watch a run go the wrong way, you say so, and the person holding that window redirects it while everyone watches the correction land. Figma for developers is the same argument, made against a tool you already know.
The agents are the other players
Several agents in one checkout is the part that needs engineering. An agent claims the paths it is about to touch, the board records one holder per path, and everyone else is refused until the holder releases it. The refusal comes from our server, so it is not something a model can talk itself out of.
Multiple AI agents on one repo has the mechanism and the numbers from our own runs.
Leaving does not stop it
Closing a tab does not kill the agents. They belong to the canvas rather than to your browser, so the work carries on and the output that arrived while you were away is there when you come back.
The code is not sitting only on that machine either. Every project gets a private repository, the work is pushed as it goes, and a machine about to be torn down pushes one last time first.
What Murmell is covers the rest of it in one page, and the home page draws the room.