Repository navigation
v1.2.0
Pauses dispatch per engine or project, with a draining stop; prints brigada history as a table; lists pinned queued jobs in brigada capacity; and keeps an automatic retry from pinning a task to an agent capped at 0. One store migration (0072, the pause table) and no new setting: once a 1.2.0 engine has opened the store, an older binary refuses it. Restart the engine and runner after you upgrade.
Changed
- The AGENTS box of
brigada toplists agents in the order of theirharness/modelname, so a row no longer moves when an agent starts or finishes a job, and its top border counts the broken and cooling agents (1 broken · 3 cooling). - The AGENTS box of
brigada topshows each agent's tier and cost weight asH×3(Hx3without UTF-8) and uses two columns only when every cell fits whole. brigada topshortens an agent name of more than two/segments to its harness and model, soopencode/zai-coding-plan/glm-5.3readsopencode/glm-5.3and the harness stays visible.- Bare
brigada historyprints a table, one row per event: time, kind, number, what happened and the title, with a landing's short commit and anafter-land failed: --task Nflag. It shows the last 50 rows, oldest first; the new--allprints every row.--task,--job,--rawand--limitprint what they did (issue #191). - The PLANS box of
brigada toplists finished plans newest first (highest plan id first) below the live plans, which keep id order, so a short terminal drops the oldest finished plans first.
Added
brigada pauseandbrigada resumepause and resume dispatch for the engine or, with--repo, one project;brigada stop --engine --drainpauses the engine, waits for its running jobs and then stops.brigada statusprints apaused:line per pause,brigada topshows it in a band of its own beside theppause, and the foreman'sstatusandcapacitytools show it; a queued job of a paused scope is counted under the pause, never asheld:(issue #198).brigada capacityprints a PINS table when queued jobs are pinned to an agent, and the foreman'scapacitytool lists the same pins: each job with its task, kind, agent, whether the pin can place (ready,coolinguntil a time,brokenorcapped_at_0) and the cap hold, if any. A wait for a slot that will free now reads apart from a pin that can never place (issue #195).- In the full-screen
brigada top, a running job's▸is a spinner on a 120 ms redraw of its own, with colour and UTF-8 and while a job runs;--intervalstill sets the fetch, a frame makes no API call, and only the lines that changed are written (issue #176).
Fixed
- An automatic retry could pin a task to an agent whose model or account cap is 0, and the task then waited forever for a free slot. Placement now skips an agent capped at 0 for the job's kind (ranked picks, retry pins, the
review.family=prefersteps and the cooling hold), and a pin on such an agent parks at the queue TTL with a reason naming the pin and the layer. A foreman turn still ignores a model capped at 0 (issue #195). - Plans parked by review leave the needs-you queue while the foreman handles them and notify when it cannot (issue #197).
brigada toplists live plans before finished ones, and a short terminal spends a free row on a running line (issue #184).