I was tired of context exchange across my claude and codex sessions, so i built a memory & coordination graph my agents can actually use
I'm a Research Engineer at a YC startup, and we ship features pretty fast. I usually run Claude Code, Cursor, Codex, and OpenCode in parallel, developing multiple features, one at a time.
The problem i noticed was that my agents had no coordination, and often confused mutual work, even when working in separate worktrees. As if they had no idea the others existed
So, I built MUON, it's a local app + mcp + cli, a mutual shared brain my agents can plug into. it drives the CLIs you already have and orchestrates them together for multi-feature execution workflows.
I'm still building it. Right now I use MUON to work on MUON, which is a weird but useful dogfood loop.
If anyone wants to poke at it, contributions are welcome. The thing I'm trying to get right is a coordination graph: shared memory and context so agents actually understand what the others (and I) already decided.
OSS Repository : https://github.com/Sweetdevil144/muon
Website : https://getmuon.com/
Docs : https://docs.getmuon.com
Product Demo : https://www.youtube.com/watch?v=oab6vByr1Jg
I've always been an open-source person, so the code is public and readable. License is Polyform Noncommercial. However, there's an extra grant on top - you can use it for your own work, including your day job, on your own machines. What it doesn't cover is turning it into the company's shared brain for a whole team (Enterprise only)