The words Murmell uses, defined
The words Murmell uses for its own parts: canvas, window, board, file reservation, collision, read link, edit link, sandbox. A canvas is one project and the room around it, a window is a real terminal attached to an agent, and a file reservation is one agent holding one path until it lets go.
Canvas
One project, and the room around it. A dotted surface in the browser holding the windows of one project. It is the unit everything else attaches to: the agents belong to the canvas rather than to your tab, the share links point at a canvas, and closing your browser leaves it running.
Window
A real terminal, on the canvas. Each window holds a terminal attached to a coding agent running on a cloud machine. What you read is what the CLI printed, in the characters it printed, and what you type goes to it.
Board
The list of who is holding which file. The server side record of every reservation, note and collision on a project. Agents talk to it through tools rather than being asked to behave: it grants a path or refuses it.
File reservation
One agent holding one path until it lets go. Before an agent writes to a file it claims the path. The board records one holder per path and refuses everybody else until the holder releases it or the claim expires. The rule lives on the server, so an agent that ignores it is refused rather than trusted.
Collision
A write to a file somebody else is holding. When a write lands on a path held by another agent, the file is snapshotted before the write goes in. Nothing is lost, and the snapshot is on the board for you to look at.
Read link
See the canvas, change nothing. A link that shows the windows, the terminal output as it arrives and the cursors of everybody else. It is free, there is no limit on how many people hold one, and it can never turn into an edit link.
Edit link
Drive an agent on somebody else canvas. A link that lets the holder type into the terminals, open windows and move things. Every action that changes anything requires it, and how many can be live at once is set by the plan.
Sandbox
The machine your agents run on. A cloud machine holding the project directory and the agent processes, and nothing else. It has no database, no decryption key and no stored credential, so an agent that escapes what it was asked to do finds a project directory and nothing to steal.
Bring your own key
Your agent account, your bill. You sign in with the agent subscriptions and API keys you already pay for. The key stays in your browser and goes only into the agent process it starts. Murmell charges for the machine and the collaboration, never for the model.