Someone just open-sourced an AI dev orchestrator they already ran in production. The numbers on it are not theoretical.
32 developers. 2 months. Multi-repo. Four AI coding assistants running simultaneously: Claude Code, Cursor, Codex, and OpenCode.
That’s the twist. Most orchestrator pitches skip the team-scale proof. This one came with it baked in.
The project is called Mutter Workspace, built by developer varnaudov. It’s a GitHub-based system that handles repository coordination, task management, and shared context across a large AI-assisted dev team. Free and open source.
Why context drift is the real problem at scale
At 3-4 people with AI, code generation is the bottleneck. At 32 people with multiple agents? It shifts. Context drift takes over.
Agents working on parallel branches start contradicting each other. They don’t know what other agents or humans already shipped. Coordination costs eat the speed gains whole.
Mutter’s answer: build the shared context layer directly into the repo. Not into a separate tool that breaks when someone forgets to update it.
How it works 🗂️
- Configure your workspace in GitHub. Mutter maps which repos belong to the project and how they connect.
- Connect your AI agents. Claude Code, Cursor, Codex, OpenCode, all reading from the same structured source of truth. 🤖
- Developers coordinate through the workspace layer, not through Slack threads or tribal memory. Tasks, context, and repo state live in one place. 🔄
- Agent-generated code lands inside a workflow that already knows the project state. Context drift drops. ✅
Pro tip
The community flagged the real differentiator fast: context lives at the repo layer. That means it’s always in sync, because it IS the project. No separate dashboard to maintain. No stale state.
If you’re running AI-assisted development with more than a handful of people, this is worth 20 minutes to evaluate. Real production proof beats any demo.
Try it: github.com/arnaudovproject/mutter 🚀
Frequently Asked Questions
Q: What’s the biggest challenge when using multiple AI tools in a large project?
Context drift between parallel branches. When different agents or team members work on the same codebase simultaneously, keeping everyone’s mental model in sync is way harder than just generating code. Mutter handles this with structured context sharing, but it’s something to watch as teams scale.
Q: Why does the post emphasize context sharing so much?
Because most failures in AI-assisted development aren’t actually about the AI being dumb, they’re about state management breaking. If agents and developers have different ideas about what changed, what’s planned, or where the architecture is headed, everything falls apart. Proper context synchronization matters more than most people realize.
Q: Do I need an orchestrator for my AI-assisted project?
Honestly, depends on scale. If you’re solo and using Claude Code, you probably don’t need it. But once you’ve got multiple developers, parallel AI agents, shared repos, and decisions piling up, keeping context aligned becomes the actual hard problem, way harder than generating code. That’s where orchestration earns its keep.
Q: Can AI really replace engineering teams?
Not at scale, not yet. AI is amazing at speeding up individual developers and automating repetitive work. But the bottleneck in big teams isn’t code generation, it’s keeping humans and agents in sync across repos and decisions over time. That’s what Mutter actually solves.
Built a workspace orchestrator for large AI-assisted projects using Claude, Cursor, Codex and OpenCode
by u/varnaudov in PromptEngineering