Launched this week
Murmell
Cloud canvas where your team and AI agents works together
112 followers
Cloud canvas where your team and AI agents works together
112 followers
Murmell is a shared cloud canvas where your team and AI agents work in the same room, on the same repo, with a preview and more coming in the future. Close your laptop and the work keeps going. Agents claim files before they write, so people and agents can move at once without overwriting each other. Run Claude Code, Codex, Kimi, and OpenCode together today, with more agents on the way (OpenClaw, Hermes, and more), and your work lands back in git, so you can always find your projects there.
Free Options
Launch Team / Built With
Murmell
Hey Product Hunt. I'm Moss'Ab, and I built Murmell.
Last year at a hackathon we had three people, four AI agents, and somehow still one laptop everyone was afraid to close.
Half the night went to "who's on which file" and "wait, my agent died when I shut the lid."
So I built Murmell: a shared cloud canvas in the browser where Claude Code, Codex, and your team work on one repo, on a cloud machine. Close your laptop, they keep going. Same room, a preview in the canvas, and the work lands back in git.
More is coming next, including iOS and Android simulators in the canvas so you can see mobile builds the same way.
I built most of this with Claude Code. Once it was solid enough, I started building Murmell with Murmell.
Launch offer: free for the first week, plus $60 of Claude Code credits.
Curious: when you ship with agents on a team, what breaks first for you, the coordination, the laptop, or the merge mess at the end?
murmell.com
you asked what breaks first. from the shared inbox side it is coordination, but not the part people expect.
the merge mess is loud. git tells you, someone fixes it, everyone learns from it. the failure that actually costs you is two actors doing the same work without colliding at all. both finish, both succeed, nothing conflicts, and you find out downstream or not at all.
we get that version every day. two people open the same conversation, both answer, the customer gets two different replies and neither of them did anything wrong. in code you would at least get a conflict. when the work leaves the system, you just get two sends.
agents sharpen it, because a person hesitates when they see someone else typing. an agent does not hesitate and does not look.
so does the canvas have a way to claim something, a file, a task, whatever the unit is, or does it show presence and leave the rest to people noticing? presence tells you someone is in the room, not what they have taken.
File level claims solve the loud half. Two agents can hold completely disjoint files and still both rewrite the same contract, one edits the caller and one edits the callee, nothing conflicts and the build breaks somewhere neither of them was looking. The thing I'd want on the page is what happens to a claim when the agent holding it dies. Nobody's at the keyboard on a cloud machine, so a stale lock is silent and it's sitting on exactly the file the next person needs.
PRISM by Block Convey
Murmell
@arun_prasad06
Hey Arun, good question.
If you mean working with your clients in the same room: yes. You can invite them onto a Murmell canvas, share the repo, and run agents there together (Claude Code, Codex, Kimi, OpenCode today).
If you mean plugging in agents your clients already run outside Murmell, that depends on which ones.
Tell me what they use and I’ll say if it’s already supported or next on the list.
PRISM by Block Convey
PRISM by Block Convey
Murmell
@arun_prasad06
Got it, thanks for clarifying.
You're describing agents that stay in the client's environment: run Claude Code there for an audit you can share, and query their DB in place so sensitive data does not have to leave.
Murmell today is the shared cloud canvas (team + agents on one repo, preview, git).
What you're asking is closer to a next step: bring that same room onto a machine or network the client already controls, instead of only through an SDK into our cloud.
I want that direction.
If you have a concrete client setup in mind (their laptop, a VPC, on-prem), tell me which and I'll say how close we are vs what we'd build first.