Getting started
Step-by-step setup for each plan. Free needs no account.
Power-Dev Pro, for one person running many agents.
- 1
Install brindle
One command on macOS or Linux. Free to use, no account needed.
curl -fsSL pawdelta.com/brindle/install | sh - 2
Sign in to your account
Connect the CLI to your account so paid features and your settings follow you.
brindle account login - 3
Upgrade to Pro
From the terminal, or from Plans and billing in your account.
brindle account upgrade - 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.
CodexSupervisor or workers; a good second-opinion reviewercodex login brindle --provider codexGoogle AntigravitySupervisor or workerscurl -fsSL https://antigravity.google/cli/install.sh | bash agyOpen-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:30bHow 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 testsMediumA normal feature or bugfixHeavyDesign-heavy or cross-cutting work, subtle bugsCheck what's ready
brindle doctor - 5
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 - 6
Add a second repo to the session
Change an API and the app that calls it in one session.
brindle repo add ../web-app - 7
Turn on build fixes
Install the GitHub app on one repo; brindle tries to fix failing builds on it.
Looking for more?
Guides and next steps that fit this setup.
Write checks that let agents run until the work is really done.
Read the guide →GuideRewind an agent to an earlier turnUndo a wrong turn and restart the worker with a note.
Read the guide →DocsConfigurationPer-repo settings: merge checks, reviewers, routing by task weight and more.
Read the docs →