run, dogfood
run
brigade run "<task>" is the aboyeur path. One orchestrator plans the work, Brigade dispatches assigned workers through their own CLIs, then the orchestrator synthesizes the final answer. It is intentionally bounded: two orchestrator calls plus the worker calls in the plan.
brigade run "review this repo and suggest the next implementation step"
brigade run "plan the migration" --dry-run
brigade run "review this repo" --show-plan
brigade run "review this repo" --verbose
brigade run "review this repo" --cwd /path/to/repo
brigade run "review this repo" --handoff
brigade run "review this repo" --read-only
brigade run "review this repo" --read-only --inspect
Common brigade run flags:
--dry-runprints planned assignments as JSON and stops before worker dispatch.--show-planprints assignments before a normal run.--verboseprints the plan, worker statuses, and synthesis status.--cwdsets the working directory for agent CLI calls.--handoffwrites a Memory Handoff for a successful non-dry run.--inspectprints the same artifact summary asbrigade runs show.--read-onlytells the orchestrator and workers to inspect and recommend only.
See The brigade run for the roster setup and adapter notes.
dogfood
brigade dogfood is the shortcut for using Brigade on itself or another trusted repo. It uses a built-in Codex-only roster, read-only prompt policy, normal run artifacts, a default Memory Handoff, and an artifact summary.
Set it up once:
brigade dogfood init --target /path/to/repo
That writes local defaults to .brigade/dogfood.toml, which is gitignored because it stores machine-local paths and preferences. New dogfood configs default handoffs to .codex/memory-handoffs/ because the dogfood roster is Codex-driven. Pass --handoff-inbox if your memory owner ingests a different path.
Daily commands:
brigade dogfood
brigade dogfood status
brigade dogfood next
brigade dogfood --target /path/to/repo
brigade dogfoodruns the configured daily path from the repo.brigade dogfood "review today's changes"overrides only the task.brigade dogfood statuschecks paths, sandbox mode, CLI availability, ignore rules, and the latest run.brigade dogfood latestshows the latest configured dogfood run.brigade dogfood nextprints the latest extracted next step.
Dogfood writes summary.md beside each run’s JSON artifacts when a final answer or next step exists. It defaults to a 600 second per-agent timeout. Trusted-workspace runs use Codex’s danger-full-access sandbox setting by default so repo inspection works on hosts where native read-only sandboxing blocks shell inspection.
Useful switches:
--no-handoffskips the dogfood handoff.--no-inspectskips the artifact summary.--native-read-only-sandboxuses Codex’s native read-only sandbox when the host supports it.
Run artifacts
CLI runs write artifacts by default under .brigade/runs/<id> below --cwd; dogfood runs use .brigade/runs/<id> below the configured target:
| File | Contents |
|---|---|
run.json | task, cwd, orchestrator, mode flags, status, artifact path, handoff path, timestamps, and duration |
roster.json | effective orchestrator, agents, limits, allow-list, and timeouts |
plan-attempts.json | raw planner outputs, parse status, and parse errors from initial/correction attempts |
plan.json | parsed worker assignments |
worker-results.json | worker status, details, and text output for non-dry runs |
synthesis.json | orchestrator synthesis status, detail, and raw text for non-dry runs |
final.txt | final synthesized answer for non-dry runs |
summary.md | dogfood summary with run metadata, final answer, and extracted next step when present |
Use --output-dir <path> to pick the artifact directory, or --no-artifacts for a throwaway run.
Inspect a completed run without opening each JSON file:
brigade runs list --cwd /path/to/repo
brigade runs latest --cwd /path/to/repo
brigade runs show .brigade/runs/<run-id>