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
PH 用户
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.
PH 用户
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.
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
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.