Squads
A Squad runs N tasks in parallel — each in its own git worktree — under a shared goal. The unit of parallel execution in Vupt.
Squads
A Squad is the unit of parallel execution in Vupt. It groups N Tasks that run concurrently under a shared goal. Each task gets its own git worktree, its own agent process, and its own journal stream.
Mental model
A Squad is a feature branch with N parallel coding sessions. When the work converges you decide which sessions to merge.
Squads do not coordinate task output automatically. They give you predictable parallelism: deterministic isolation per task, real-time visibility per task, explicit merge gates per task. The orchestration logic lives in the conflict prediction layer that scans diffs across tasks and warns you before merging colliding changes.
Lifecycle states
| State | Meaning |
|---|---|
draft | Squad created, tasks not yet launched |
running | At least one task is actively running |
awaiting-review | All tasks finished; user reviews diffs |
merged | At least one task's diff was merged |
discarded | All tasks discarded; worktrees cleaned up |
archived | Read-only historical record |
Worktree layout
Vupt creates one worktree per task under ~/.vupt/worktrees/<squad-id>/<task-id>/. The worktree is a real git worktree (git worktree add) so any local tooling that operates on a checkout works unchanged.
# Inspect a Squad's worktrees from the host shell
git worktree list | grep .vuptLimits
| Tier | Max parallel agents per Squad |
|---|---|
| Free | 2 |
| Pro | unlimited |
| Team / Business | unlimited |