The Dream: Parallel AI Coding
You have a complex task — refactoring an auth module that touches 12 files across your API, frontend, tests, and docs.
A single AI agent (Claude, Copilot, Cursor) would take 20-30 minutes. It might hit context limits. It processes files sequentially.
So you think: "I'll just open 5 terminals and split the work."
The Reality: 5 Minutes of Chaos
Terminal 1: Starts refactoring auth.rs
Terminal 3: Also starts editing auth.rs
→ ❌ File conflict. One overwrites the other.
Terminal 4: Writes tests importing a function from api.rs
Terminal 2: Hasn't written that function yet
→ ❌ Dependency failure.
Terminal 5: Documents the /auth/login endpoint
Terminal 3: Just renamed it to /auth/signin
→ ❌ Stale reference.
Without coordination, parallel AI coding is worse than sequential. You save time on execution but lose it on conflict resolution.
Why Existing Solutions Don't Fit
Multi-agent frameworks (AutoGen, CrewAI, LangGraph):
These coordinate conversations between agents. They're great for generic multi-agent workflows. But they don't manage file locks, dependency ordering, or codebase-level conflict prevention.
Manual coordination:
You become the scheduler. You decide which terminal works on which file. You check for conflicts. You manage dependencies. Congratulations — you are now the bottleneck.
Single agent:
Safe but slow. No parallelism. Hits context limits on large tasks.
What's Actually Needed
The problem isn't the AI — Claude writes great code. The problem is orchestration:
- Task decomposition: Breaking a vague request into concrete, parallelizable sub-tasks
- Dependency management: Knowing which tasks must finish before others can start
- File locking: Preventing two workers from editing the same file simultaneously
- Monitoring: Seeing what every worker is doing in real-time
- Recovery: Handling failures without manual intervention
None of these require intelligence. They require determinism.
Our Approach: Jupiter
We're building Jupiter — a Rust-powered orchestration engine for parallel AI coding agents. One command. N workers. Zero conflicts.
The key insight: orchestration doesn't need AI. Scheduling, locking, monitoring, and routing are deterministic operations. We write them in Rust (zero tokens). Claude is only used for planning and writing code.
More architecture details coming this week.
Website: jupiteros.ai
Discord: discord.com/invite/Sekuexw3
Top comments (0)