Multi-Hive concurrency

A Hive is scoped to one project, but you are rarely working on just one thing. SwarmADE lets you keep several Hives open and active at the same time, each with its own folder, its own Swarm of Workers, and its own Queen state.

Why run multiple Hives

Concurrency maps to how real work happens:

• Parallel features — drive two efforts in the same codebase from separate Hives without their tasks colliding.
• Multiple repositories — a frontend Hive and a backend Hive can advance in lockstep while you review both.
• Background vs. foreground — let a long-running refactor churn in one Hive while you focus on another.

Color coding makes this practical: give each Hive a distinct color so you can tell them apart instantly. See Color coding & customization.

How the Queen keeps them separate

Each Hive has its own Queen state. The Queen plans, decomposes, and tracks the work for one Hive independently of every other Hive — one Hive’s plan and timeline never bleed into another’s. The Workers in each Hive run in their own local terminals, so concurrent Hives stay fully isolated end to end.

Hive A ─ Queen state A ─ Swarm A ─┐
                                  ├─ run concurrently, fully isolated
Hive B ─ Queen state B ─ Swarm B ─┘

Plan gating

How many Hives you can run at once depends on your subscription. The limit rises with the tier — Starter is the most constrained, Pro allows more, and Ultra the most.

Running several Hives in parallel is one of the biggest productivity wins in SwarmADE — pick a tier that matches how many projects you keep in flight, and use color coding to stay oriented across all of them.