← home · use cases
what a crash-safe fleet is actually for.
The point of a durable event log, lock leases, and a merge queue is not the primitives — it's what they let you run. Here are the jobs people reach for brat to do.
Parallel bug triage across a codebase
Point the Mayor at src/, let it file one task per bug, and run a fleet of agents to fix them at once.
read the workflow →
evaluationRunning a multi-engine bake-off
Give the same task to Claude Code, Aider, and Codex at once and compare the branches side by side.
read the workflow →
refactorOvernight refactor fleet
Queue a large mechanical refactor as dozens of tasks and let the fleet grind through it while you sleep.
read the workflow →
merge queueA CI-gated agent merge queue
Let agents propose branches all day, and land only the ones that pass your existing CI, in order.
read the workflow →
scale-upGraduating from tmux panes
Move from counting tmux panes to querying an event log once the fleet outgrows your screen.
read the workflow →
governanceAuditable, reproducible agent runs
Keep an immutable record of every task, session, lock, and merge for review and reproducibility.
read the workflow →
don't see yours?
If you're running agents in parallel on a real repo, brat probably fits. Tell us your setup.