Getting started

Step-by-step setup for each plan. Free needs no account.

Developer Core. Everything runs on your machine; no account required.

1
Install brindle
One command on macOS or Linux. Free to use, no account needed.
```
curl -fsSL pawdelta.com/brindle/install | sh
```
2
Try it on a practice repo (optional)
Watch the whole loop once before pointing it at your own code.
```
brindle demo
```
3
Start it in a repository
brindle init finds your setup and test commands; brindle opens the supervisor, which plans the work and hands parts to workers, each on its own branch.
```
cd ~/code/myapp
brindle init
brindle
```
4
Choose your agents
brindle uses the agent CLIs you already have, signed in your own way, and mixes them in one session. One is enough to start. Your code goes only to the providers you pick.
Claude CodeSupervisor (the default) and workers
claude auth login
Claude Code docs ↗
CodexSupervisor or workers; a good second-opinion reviewer
codex login brindle --provider codex
Codex CLI ↗Codex reviews Claude (guide)
Google AntigravitySupervisor or workers
curl -fsSL https://antigravity.google/cli/install.sh | bash agy
Antigravity in the docs
Open-weight modelsWorkers and reviewers, on your own machine. Qwen3-Coder 30B needs about 20 GB of GPU memory.
brew install ollama ollama pull qwen3-coder:30b
Local models guide Download Ollama ↗
How work gets shared out
The supervisor sizes each task, and brindle sends it to a signed-in agent for that size. Agents that aren't signed in, or are near their usage limit, are skipped.
LightDocs, renames, simple tests
MediumA normal feature or bugfix
HeavyDesign-heavy or cross-cutting work, subtle bugs
Check what's ready
```
brindle doctor
```
Providers and models docs Routing by weight (configuration)
5
Give it a goal
Describe what you want built. Workers run in parallel and nothing merges until review and your checks pass.
6
Check what it cost
Spend is tracked on this computer.
```
brindle cost report
```