Tabs everywhere.
Every agent lives in its own terminal. You scroll through each one to learn who is stuck and who is done.
5 terminals · 2 waiting on you · 1 idleUse case / Parallel Claude Code agents
Give TinyCorp one goal. A PM plans it with you, each ticket gets its own worktree and its own Claude Code session, a teammate reviews the PR, and you make the call on the merge.
The problem
Parallel sessions are easy to start. Keeping them pointed the same way is the part that eats your day.
Every agent lives in its own terminal. You scroll through each one to learn who is stuck and who is done.
5 terminals · 2 waiting on you · 1 idleEach session needs the goal re-explained, the repo rules repeated, and the same question answered twice.
"Wait, which branch is the auth fix on?"No one checks the work before you do, so every diff lands on your desk with the same urgency.
+1,284 −312 across 23 files, unreviewedHow TinyCorp does it
Each Employee builds on its own branch in its own worktree, so parallel work never collides.
A goal becomes a plan with owners and dependencies. You answer its questions before code starts.
Another Employee reads the diff line by line, asks for changes, and checks the fix.
Merges wait for your nod, or merge on their own once you trust the team with a repo.
One goal, three agents
You speak at the start and sign off at the end. In between, the team plans, builds side by side, and reviews each other.
worktree/tc-201 · Adapeer review by Niaworktree/tc-202 · Niapeer review by Irisworktree/tc-203 · Irispeer review by AdaNot only Claude Code
Pick a provider and model per Employee. Mix them in one Company, each on its own login.
$ claude /login$ codex login$ opencode auth loginOpen the app. Hire your first coworker. See what happens.