Gemini
OpenCodeWork together
Collaborate with your team live
Share one canvas instead of passing screenshots around. Everyone sees the same terminals, cursors and preview while the work is happening.
MCheckoutmain syncedSearch commands ⌘ KShare
AdaJun
Claude Code working✶ Claude Code❯ Make checkout recoverablesrc/Checkout.tsx⎿ Read src/Checkout.tsx● Tracing payment states…⎿ Edit src/Checkout.tsx +38 −12✻ Cooked for 2m 18smain0 collisions
Codex working›_ OpenAI Codex› Refactor preview lifecyclesrc/Preview.tsx• Explored 7 files• Claimed src/Preview.tsx↳ Edited preview recovery✓ 24 tests passedmain0 collisions
Kimi working◈ Kimi Code❯ Unify the design systemsrc/styles/app.css✦ Scanning tokens and surfaces╭ src/styles/app.css╰ Responsive grid updated +18 −6✓ Ready for reviewmain0 collisions
Cursor Agent working◆ Cursor Agent› Polish the onboarding flowsrc/onboarding/Welcome.tsx↳ Searched onboarding routes● Updating first-run copy…+ Added transition states✓ Lint cleanmain0 collisionsDemo
Stay in control
Run every coding agent in one canvas
Open Claude Code, Codex, Kimi and more in the same project. Move, resize and follow each session without losing the thread.
MCheckoutmain syncedSearch commands ⌘ K3 workingShare
One file. One editor.
When two agents reach the same file, Murmell lets one edit while the other waits. No overwritten work, no manual coordination.
Claude Codeclaims the fileCodexcontinues safelyCodexwaits at the lockThe canvas makes parallel agents understandable before it makes them faster.
I can close my laptop, come back later, and the whole build is still where I left it.
It feels less like supervising terminals and more like working in the same room.
I finally know what every agent is doing without opening four different tools.
Sharing the live room is much clearer than sending another terminal recording.
The project stays warm in the cloud, so returning to the work takes seconds.
File reservations make parallel work feel controlled instead of risky.
Watching the canvas tells me more than another stream of agent logs ever did.
It is the first multi-agent setup I can explain to a teammate in one screen.
I can move between Claude and Codex without losing the state of the project.
Plans
Starter
1 hour free. The whole canvas.
$0to get started
No card. No automatic subscription.
The full Pro Canvas, for one hour.
- 20 agent windows per person
- One live canvas, unlimited projects
- Every supported coding agent
- Live collaboration and shared context
Bring a project. Connect your agents.
Pick up where you left off with Pro.
Pro
Make it your everyday workspace.
$39.20/month
$470.40 billed yearly. Save 20%.
Your agents. Their memory. One place.
- 20 agent windows per person
- One live canvas, unlimited projects
- Every supported coding agent
- Persistent agent memory
- Inter-agent messaging and coordination
- Resume sessions, including Claude
- Shared file protection
- Live collaboration and previews
Teams
Save 36%All of Pro. Your team, on one bill.
$125.44/month
$31.36 / person / month
$2,352 Save $846.72 / year
$1,505.28 billed yearly
Enterprise
A workspace built around your company.
- Private cloud or on-prem, on request
- Custom seats, security and support
Connect your own provider accounts. Provider usage is billed separately.
06 / 06
FAQ
What is Murmell?
Murmell is a browser canvas where several AI coding agents (Claude Code, Codex, Kimi, OpenCode) run on a cloud machine and share one project directory. Each agent opens in its own window with a real terminal, and everyone on the link sees the same canvas as it happens.
Can several people really use one canvas at the same time?
Yes. Everyone on the link sees the same room: who joined, which window they are watching, where their cursor is. Each person drives their own agents, and nothing has to be replayed or refreshed to stay in step.
Where does my code live?
On a machine Murmell runs, in one directory, and in a private GitHub repository created with the project. The workspace is disposable and the repository is not: the work is pushed before a machine is ever torn down.
How much does Murmell cost?
Murmell Starter includes the full Canvas and one hour of cloud time, with no card and no automatic subscription. Murmell Pro is $49 per month for Canvas or Bots, and $79 per month for Canvas + Bots. Murmell Bots and the bundle are coming soon. Pro starts with 30 days free and includes 20 agent windows per person, one open canvas, and unlimited projects. Pro Canvas annual billing is $470.40 per year, saving 20%. Teams starts at four people at $39.20 per person per month, saving 20%. With annual billing, both discounts combine: $376.32 per person per year, saving 36% versus monthly Pro. Enterprise pricing is available on request.
What are Murmell Bots?
Murmell Bots are autonomous cloud agents for tasks and routines. They will work without an open Canvas and reuse the provider connections already linked to Murmell. Bots and the Canvas + Bots bundle are coming soon.
Do you resell tokens?
No. You connect the agent subscriptions and API keys you already pay for. Murmell charges for the machine and the collaboration, never for the model.
What stops two agents destroying each other?
An agent claims the paths it is about to touch before it writes. A watcher attributes every write back to whoever made it, and a colliding write is snapshotted before it lands, so nothing is lost. The rule is enforced by the machine rather than suggested to the model.
Is each project isolated?
Yes. Every canvas runs on its own machine, separate from every other project Murmell hosts. The machine that executes agent code holds no database and no decryption key.
Which coding agents does Murmell support?
Claude Code, Codex, Kimi and OpenCode today, each in its own terminal on the canvas, signed in with your own account or API key. Adding an agent is adding a tile: nothing about the canvas changes.
Can I self-host it?
No. Murmell runs the machines for you. That is the product. Your code still ends up in a private repository you own.