I often run Claude Code and Codex side by side. Murmell lets them work in the same cloud workspace, with real terminals and file reservations, so I can see what each agent is doing without switching between multiple terminal windows.
The persistence worked well in my test. I started a shell command that waited 45 seconds before writing a completion marker to a file, left the project, and closed the browser tab. When I returned, the same Claude Code session was restored, the command had finished, and the file was still there.
It is more than a small multi-agent wrapper. Murmell keeps the workspace, terminal sessions, agent coordination, and Git snapshots together in one browser canvas.
Murmell
@moss_ab_mirande_ney Amazing update.. the unified agent memory sounds incredibly useful. congrats
Murmell
@priya_kushwaha1 Thanks !!!
We keep working to add some useful features in the future !
Rebuilding the whole thing after the first launch broke it, at 19. That is not a small thing. Congrats.
File claiming caught my eye. If an agent claims a file and then dies, who lets go?
Murmell
@niveditha_patluri1
Great question. File claims are leases, their are not permanent locks.
By default, a claim lasts 15 minutes and is automatically renewed while the agent is active through board calls or observed file writes. If the agent crashes or disappears, the lease stops renewing and
expires, so another agent can safely claim the file.
We currently rely on lease expiration rather than a manual override to avoid confilcts.
I'm curious where you're finding this most useful. Is it for intentional pair programming, or just collabing on the same code base with agents? Or, sometimes I set multiple agents to work on the same repo simultaneously and don't want them to conflict either.
Great!!
That would definitely be useful since I work with Claude Code and Codex at the same time.
Murmell
And don't forget, you can maybe win 1000$ worth of claude credits 👀👀
Seeing each other's cursors and terminals live sounds great, although does that get overwhelming once you've got like 4/5 agents all moving around the same workspace at once?
Meridian
Building a reliable shared workspace for multiple developers and coding agents is a difficult problem. How does file claiming recover if an agent crashes or disconnects before releasing a file? Is there a timeout or manual override to prevent the file from remaining locked?
Murmell
@adityaharish2002 Thank you, I really appreciate that. If an agent dies while holding a file, the claim does not stay forever.
Claims expire after 15 minutes by default and are renewed only while the agent is still active. Once the lease expires, another agent can take over the file.
This recovery mechanism was essential because agents do crash, disconnect, or simply forget to release their work.