Getting started

Your org is on Enterprise. You sign in through your company.

1. 1

   Sign in with your company account

   Your org uses SSO, so sign in to your account with it first.

   Open Home in your account →
2. 2

   Install brindle

   One command on macOS or Linux. Free to use, no account needed.

   curl -fsSL pawdelta.com/brindle/install | sh

   Copy
3. 3

   Sign in the CLI

   This opens your company's sign-in page.

   brindle account login

   Copy
4. 4

   Sign in to your company's cloud, if asked

   If your org routes models through its own cloud (Bedrock, Vertex or Azure), brindle doctor says so and shows the one command to run, for example:

   aws sso login --profile halyard
   brindle doctor

   Copy
5. 5

   Choose your agents

   Your org's admins choose which agents and models are allowed; brindle only offers those. Sign in to the ones you'll use. brindle doctor shows what's open to you.

   Claude CodeSupervisor (the default) and workers

   claude auth login

   Copy

   Claude Code docs ↗

   CodexSupervisor or workers; a good second-opinion reviewer

   codex login
   brindle --provider codex

   Copy

   Codex CLI ↗Codex reviews Claude (guide)

   Google AntigravitySupervisor or workers

   curl -fsSL https://antigravity.google/cli/install.sh | bash
   agy

   Copy

   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

   Copy

   Local models guideDownload 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

   Copy

   Providers and models docsRouting by weight (configuration)
6. 6

   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

   Copy