Getting started

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

← Team: choose admin or member

Admin setup · Team

DevOps Automation. You're setting the team up.

  1. 1

    Install brindle

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

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

    Sign in to your account

    Connect the CLI to your account so paid features and your settings follow you.

    brindle account login
  3. 3

    Create the team

    Pick the seat count now; you can change it later under Settings › Billing and seats.

    brindle account upgrade --team --seats 10 --org acme
  4. 4

    Invite your developers

    Invite by email from Members. Each invite shows a code once.

  5. 5

    Set a monthly budget

    For the org, each role, or one person.

  6. 6

    Choose which agents and models your org can use

    Allow providers (Claude Code, Codex, Antigravity, open-weight) and the models within them. Your members' brindle only offers what you allow.

  7. 7

    Set org policy

    A worker cap, and whether human review is required before a merge.

  8. 8

    Connect brindle CI

    Install the GitHub app on your repos. Label an issue to get a PR.

  9. 9

    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
    CodexSupervisor or workers; a good second-opinion reviewer
    codex login
    brindle --provider codex
    Google AntigravitySupervisor or workers
    curl -fsSL https://antigravity.google/cli/install.sh | bash
    agy
    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

    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

Looking for more?

Guides and next steps that fit this setup.