brindle 0.3.19

Released Oct 14, 2026 · All releases

New for everyone

• brindle asks which CLI runs the supervisor. The first brindle shows a short picker (Claude Code, Codex, Antigravity) and remembers your pick. After that it starts straight away and prints one line naming the CLI. It asks again only if your pick is no longer signed in or allowed. brindle -s opens the picker any time; brindle -s codex switches directly. Scripts, CI, --yes and brindle demo never get a prompt.
• Sign in from the picker. Choosing a CLI you haven't set up installs it if needed, opens its sign-in and checks it worked, then carries on.
• Pick worker models per task size. Press w in the picker to choose the model for light, medium and heavy tasks: through a CLI you're signed in to, locally with Ollama, or hosted with an API key. A model that isn't ready is set up right there.
• Local models set themselves up. Picking an Ollama model checks this machine has the memory for it, installs Ollama only after asking, downloads the model with progress, and checks it answers. If the machine is too small or you say no, brindle falls back to another model and says why.
• API keys are checked before they're stored. brindle keys set (and the picker) shows where to get the key, takes it from a hidden prompt, and checks it with the provider without generating anything: OpenRouter also shows the credit left. A rejected key gets a clear message and nothing is stored. Keys stay in this machine's keychain.

For Team and Enterprise

• Only what you're allowed to use. The picker and the workers screen list only the CLIs and models your org allows for your role, following its managed routes and whether personal API keys are allowed. -s with anything else is refused, and saved worker picks are checked again at every launch.

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