EddieFree tool · Eddie’s Workshop
Run several agents without the chaos.
Tell the planner what you’re building and how many agents you want to run. It splits the work into lanes, orders them, and points out where they’ll collide.
Free · no sign-up · updated October 2026
Your plan shows up here.
The rules the planner follows
Contracts first. Shared types, API shapes and database changes are agreed in a short first phase, because every lane depends on them.
One owner per file. Two agents editing the same file is the most common way parallel runs go wrong. Shared files like lockfiles, route indexes and migrations get a single owner.
Merge one lane at a time. Integrate, run the tests, then take the next one. When something breaks, you know which lane did it.
Fewer agents than you think. Every extra agent is another diff to review. Two or three focused lanes usually beat five that keep waiting on each other.
Made by Eddie
Stop checking on your agents.
Several agents at once is exactly what Eddie is for: one look at the notch shows who’s working, done or stuck.
Questions.
How many AI coding agents should I run at once?
Start with two or three. The limit is usually your review time, not the agents: each lane produces a diff you need to read and test.
How do I stop parallel agents from editing the same files?
Give each agent a list of files it owns and tell it to ask before touching anything else. Separate git worktrees or branches per agent help too.
Does the planner use AI?
No. It’s a rule-based planner that runs in your browser. It doesn’t read your code, so treat the plan as a starting point.