Command Reference & Gameplay Guide
| Command | Description |
|---|---|
swarm init |
Initialise Swarm in your project |
swarm setup-ci |
Configure CI triggers for your platform |
swarm process <N> |
Process issue #N through the full pipeline |
swarm review <N> |
Review PR #N through the review pipeline |
swarm worktrees |
Open worktree dashboard in browser |
swarm worktrees list |
Show worktrees as a terminal table |
swarm worktrees clean |
Remove stale worktrees interactively |
swarm help |
Show help message |
The main event. Takes a GitHub issue number and runs it through the full agent pipeline: scope, dev, review, and rework.
swarm process 42
| Flag | Description |
|---|---|
--max-rework N | Max review/rework cycles (default: 3) |
--dry | Show what would happen without running agents |
Review an existing pull request without running the full pipeline. Useful for PRs created manually or by other tools.
swarm review 15
| Flag | Description |
|---|---|
--max-rework N | Max rework cycles (default: 3) |
--review-only | Post review findings without reworking |
--dry | Preview without running agents |
Manage the git worktrees that agents create. See what's active, what's stale, and clean up after completed runs.
swarm worktrees
Opens an HTML dashboard in your browser showing all agent worktrees with status, disk usage, PR links, and staleness indicators.
swarm worktrees list
swarm worktrees clean # Interactive
swarm worktrees clean --dry # Preview only
swarm worktrees clean --all # Remove everything
swarm worktrees list --json # Pipe to jq, scripts, etc.
A worktree is marked stale if any of these are true:
| Status | Meaning |
|---|---|
| active | Open PR or commits within 3 days |
| aging | 3+ days old, or no PR but recent activity |
| stale | Meets any staleness criteria above |
In production, you don't run swarm process manually. CI does it for you. When an issue is assigned, labelled, or @mentioned, the CI workflow fires swarm process automatically.
Supported platforms: