Skip to content

v1.1.0

Choose a tag to compare

@github-actions github-actions released this 04 Nov 23:17
· 163 commits to main since this release
2ac6c2d

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 top is 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 top shows 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 shows awaiting approval, reviewing round N or needs 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 top lists agents in two columns: a green ●, a yellow ↺ with until HH:MM or 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 carries all ≤ global N, M off or all ready.
  • brigada top lists events one per row, newest on top, in plain words such as #328 landed and plan #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 top ends in the command that answers it, whole: → brigada plan approve N, → brigada land approve N, → brigada push approve or → brigada agent reset <harness>/<model>. The reason is cut instead.
  • brigada top has a screen for each state: a first run shows the command to type, a view with no live plan reads none live · N finished with the time of the last landing, an engine it cannot reach shows a red ✗ ENGINE UNREACHABLE band 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 || PAUSED band and freezes the job ages.
  • brigada top fits 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 top shows one scope in every section: with --project that 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 history prints plain words by default: each line starts with its local time as MM-DD HH:MM and says what happened, and the bare view shows only those events. --task N and --job N show every item, with a worker's result as its status and summary and a review's findings in full. The new --raw flag 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 ask returns at once, the reply is the foreman report: line of brigada status, and the answer goes back with another brigada ask. They also name brigada logs --task N, the engine restart after an upgrade, and landing by hand and brigada budget --wakes among 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 at needs_foreman, the foreman reaches the user through its report, and ask_user records a question and parks nothing (issue #173).

Added

  • check_log, a foreman tool (issue #180): it reads a job's whole check log, by job with offset and limit in bytes, the last 16 KB by default and at most 64 KB a read. The default foreman.md tells it to read the log before it calls a failure a flake: a rerun of brigada init brings that text to a project that has not edited its file, and brigada init --take-default foreman replaces 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_limit error kind and a reason such as output limit reached: 32,000 tokens, 31,951 of them reasoning, restarts on another agent without raising effort, and parks at needs_foreman with 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_log reads (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_holds list, and a task_unattended event 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 changes verdict left the plan parked with no explanation. A plan_verdict_unanswered event 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.sh no 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, so gh needs write access to Actions (issue #168).
  • Two flaky tests: TestInitCodexDiscoverySafety and TestRunnerToolCallSuspendsStallClock no longer fail on a busy machine (issues #175 and #179).