Repository navigation
v1.1.0
A rebuilt brigada top, a readable brigada history, and fixes that name failures brigada used to hide. No store migration and no new setting. Restart the engine and runner after you upgrade.
Changed
brigada topis rebuilt as one column of rounded boxes (issue #162): NEEDS YOU first, then FOREMAN and JOBS when they have lines, PLANS, AGENTS and EVENTS. A two-row header carries the brand mark, scope, uptime, clock and keys, then a slots meter with the run, queue, held and needs counters. The keys, flags and piped snapshot stay as they were.brigada topshows the state of the work. An active plan shows one cell per task,■■■■■■□□ 3/8, with a legend in the PLANS border; a plan that is not active showsawaiting approval,reviewing round Norneeds foreman; cancelled and retired tasks leave the total. Every job sits under its plan in fixed columns: task, title, kind, agent, age, last event. A done task waiting to land keeps a⇡line, and needs-you and running rows sit on a dark red and a dark blue at 256 colours and true colour.brigada toplists agents in two columns: a green●, a yellow↺withuntil HH:MMor a red✗with its reason, the name, then one cell per slot of the effective cap, filled up to the running count. A running agent's name and its job line take the family colour. The AGENTS border carriesall ≤ global N,M offorall ready.brigada toplists events one per row, newest on top, in plain words such as#328 landedandplan #99 done, with no job bookkeeping. The first line of the foreman's report sits in the EVENTS border.- A needs-you line in
brigada topends in the command that answers it, whole:→ brigada plan approve N,→ brigada land approve N,→ brigada push approveor→ brigada agent reset <harness>/<model>. The reason is cut instead. brigada tophas a screen for each state: a first run shows the command to type, a view with no live plan readsnone live · N finishedwith the time of the last landing, an engine it cannot reach shows a red✗ ENGINE UNREACHABLEband with the age of the data and dims everything below it so old data does not read as live, and a pause shows a yellow|| PAUSEDband and freezes the job ages.brigada topfits the terminal: the frame never has more lines than the height, and lines drop class by class, finished plans before queued tasks and queued tasks before running ones, with the header and NEEDS YOU last. Rows are measured in terminal cells, so wide characters no longer break a box. Every glyph has an ASCII fallback, and with no colour each plan-cell state keeps its own glyph (issue #182).brigada topshows one scope in every section: with--projectthat project, except that a broken agent still shows; without it the whole engine, with each plan line naming its repo when more than one project shows. The header names the scope in place of the pid.brigada historyprints plain words by default: each line starts with its local time asMM-DD HH:MMand says what happened, and the bare view shows only those events.--task Nand--job Nshow every item, with a worker's result as its status and summary and a review's findings in full. The new--rawflag prints the earlier form unchanged.- The capacity AGENTS table shows each agent's effective cap: its own runner, account and model caps with the global layer folded in, naming the layer that binds it. Plan caps stay out of the fold.
- The operator guide and skill cover the way back from the foreman:
brigada askreturns at once, the reply is theforeman report:line ofbrigada status, and the answer goes back with anotherbrigada ask. They also namebrigada logs --task N, the engine restart after an upgrade, and landing by hand andbrigada budget --wakesamong the user's decisions. - The docs no longer say a task parks at
needs_user: the state is reserved and no path enters it. A task that needs judgment parks atneeds_foreman, the foreman reaches the user through its report, andask_userrecords a question and parks nothing (issue #173).
Added
check_log, a foreman tool (issue #180): it reads a job's whole check log, byjobwithoffsetandlimitin bytes, the last 16 KB by default and at most 64 KB a read. The defaultforeman.mdtells it to read the log before it calls a failure a flake: a rerun ofbrigada initbrings that text to a project that has not edited its file, andbrigada init --take-default foremanreplaces an edited one.
Fixed
- A run of opencode cut off at its output token limit read as a run with no result. It now fails with the
output_limiterror kind and a reason such asoutput limit reached: 32,000 tokens, 31,951 of them reasoning, restarts on another agent without raising effort, and parks atneeds_foremanwith that reason when no retry applies. A run that still ended with a readable result block stands (issue #172). - A failed land check told the foreman the start of its output, cut to 500 bytes, which was often noise. The event now keeps the end of the log, where the failure is, and names the land job whose log
check_logreads (issue #180). - A task the foreman is already handling no longer shows under NEEDS YOU or raises a banner (issue #166). The task appears in a new
foreman_holdslist, and atask_unattendedevent announces a park the foreman will not handle, once. - A worker under a limited shell scope could decide it had no shell and stop: the worker prompt now names the commands in scope, and says that a refusal covers one command, not the shell (issue #167).
- A done foreman turn that swallowed a plan's
changesverdict left the plan parked with no explanation. Aplan_verdict_unansweredevent now names the plan, the round and the turn, and the needs-you entry heads its findings with the same turn (issue #164). scripts/land-ready.shno longer reads a CI job that GitHub never gave a runner as failed CI. It reruns the failed jobs and waits, up to three attempts, then holds and says why. The gate now writes, soghneeds write access to Actions (issue #168).- Two flaky tests:
TestInitCodexDiscoverySafetyandTestRunnerToolCallSuspendsStallClockno longer fail on a busy machine (issues #175 and #179).