Working in parallel — several worktrees running at the same time — is the habit Unstoppable Code is built around. Instead of starting one task and waiting for it to finish, you start several, let them run concurrently, and check on each as it frees up. This article covers how to do that and how to stay oriented while you do.
Why work in parallel
A single agent leaves most of your time, and most of your subscription, idle: you ask for something, then you wait. Running work in parallel is how you actually use the capacity you're paying for. In practice you might have five to ten tasks going at once.
Start more than one task
Because each worktree is an isolated branch and checkout, tasks never step on each other. So you don't have to wait for one to finish before starting the next — start a task, then start another, and let them run at the same time.
Keep work moving
The goal is that nothing sits idle. Keep each task moving to its next step — implementation, code review, or testing — rather than leaving it parked.
A simple way to build the habit: before you step away, fire off a few things — a chat or a pipeline — so work continues while you're gone. When you come back, you pick up each one where it left off.
Read the status indicators
You don't watch agents work. Instead, the app surfaces what's happening so you can step away and come back:
Status indicators show the state of each item at a glance — a plan waiting, a pipeline running, a finished pipeline you haven't opened yet, or a task that's done and needs your attention.
Toast notifications let you know when something needs attention, so you don't have to sit in the app.
Stay oriented while you're juggling
Context-switching across many worktrees is the hard part of working this way — it's easy to lose track of which task is which. A quick preview of a task, just enough to remind yourself what it's about, helps you re-orient before you act, so you don't send a message to the wrong worktree. See Multitasking without losing context for more.
Testing is usually the bottleneck
Once everything is moving, one bottleneck tends to remain: testing.
Agents keep work flowing right up until something needs to be verified. Building automated verification into your project — so agents and CI can confirm their own work — is what keeps the pipeline from stalling there.
Next steps
Keeping your backlog flush — queue work before you step away so agents are always busy.
Planning mode & plan tracking — plan bigger changes before you build them.
Core concepts & vocabulary — the terms behind this workflow.