Explained

Claude Code in the browser

Claude Code runs in a browser tab on Murmell. The window on the canvas is a real terminal attached to the real CLI, and the CLI is running on a cloud machine rather than on the computer in front of you. The tab is a view of the session, not the session itself.

So there is nothing to install, and closing the tab does not end the run.

Nothing to install

No CLI to keep current on your machine, and no shell to be in before you can start. You open the canvas, open a window, and the agent is there. Any computer with a browser reaches the same canvas.

The tab is not the session

Close it and the agents keep going. Come back later and the same windows are where you left them, with the output that arrived while you were away. That falls out of running the agents on our machines instead of in your tab. Run Claude Code in the cloud is the machine side of it.

Real terminal output, not a transcript of it

The window shows what the CLI printed, in the characters it printed. You are reading the tool rather than a summary of the tool, which matters the first time an agent asks you something and you need to see exactly what it saw.

More than one window

Because the agents are not on your computer, five of them side by side cost you nothing local. They also share one project directory, which is the part that needs a rule: an agent claims the paths it is about to touch, and the board refuses everyone else until it releases them.

Multiple AI agents on one repo explains the board. The canvas on the home page shows the windows.

Somebody else can open the same tab

A canvas has a link, and whoever opens it sees the windows and the terminals live, with named cursors on the ones who are looking. Read links are free and there is no limit on them, so showing a colleague what an agent is doing costs a paste. Multiplayer coding with AI agents is that part, and Figma for developers is the same idea against a surface you already know.