Skip to content

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 04 Nov 12:28
· 127 commits to dev since this release

Fixed

  • orq rounds now counts review findings written with a leading bold severity (**Bloqueante**, **Sugestão — file:7–8:**, PT/EN),
    not only [blocker] tags, and reads markdown-link paths, en-dash line ranges and per-round .worktrees/<dir>/ prefixes so
    the same file matches across rounds.
  • orq quota no longer reports the antigravity login as expired after an hour idle: the access token only lives 1h
    and agy renews it on its next run, so with a refresh token in the keyring the note is "token idle (agy refreshes on
    next run)" and orq pick keeps the account. "login expired" stays for a missing refresh token or an API 401.

Changed

  • install.sh --uninstall now also runs systemctl --user disable --now on the orq timers.
  • orq pick limits: 95% of the week (policy.quota_week) and, on the 5h window, 90/85/80% for simple/medium/heavy
    tasks (policy.quota_5h), for every agent. An agent is never picked to review or give an opinion on its own code,
    whenever another declared agent exists for the role. policy.quota_limit caps the 5h pick limit and sets the ! in orq quota --line.
    Migration: quota_limit used to also cap the weekly window; it now only caps 5h, so configs that lowered it to
    keep accounts away from the weekly limit should set policy.quota_week explicitly instead.
  • orq quota's human reset times ("resets 14:30") moved from right after each window to the end of the line, so
    <name> 5h=NN% week=NN% always stays intact and easy to grep.

Added

  • orq rounds <ID> [-w <workspace>] [--json]: watchdog metrics per issue with no LLM, from the files in
    .orquestra/<ID>/ (fix-<n>.md, review-*.out.md): fix rounds vs policy.max_rounds, time total and per round,
    reviewer findings that come back across rounds (same file + word overlap) and an alert level (ok / warn / stop).
    orq board shows a marker such as r2/2 ⚠ next to each conductor's issues.
  • Scope guideline in the /issue skill and the workspace CLAUDE.md template: split big issues into sub-issues or
    sequential batches (one PR each) before dispatching, and stop and split when reviews hit policy.max_rounds.
  • Pacing in orq pick: an account whose usage, at the pace so far in a window (used ÷ elapsed share, needs the reset
    time and 10% of the window elapsed), projects past that window's pick limit at the reset loses policy.pacing_penalty
    (default 0.3, 0 = off) of score. Soft: the hard limits are unchanged; fixed roles are not scored.
  • headroom = N in an [agents.<name>] section: children are dropped from that agent's accounts once usage reaches
    the limits minus N points (5h and week), leaving that share for conductors; account choice respects it.
  • orq pick skips an agent whose quota reading says the login expired, with the fix command as the reason
    (e.g. antigravity: login expired: run `agy models` ); orq quota keeps showing it.
  • orq ci [-w <workspace>]... [--json]: CI/CD signal per claimed issue with a PR — queued, running, passed, failed
    or none, from gh pr view's checks on the branch the issue's worktree carries, collected live (it's the user
    asking right now). Cached in the state dir like quota; orq board reads that same cache for a new CI column
    and never blocks on the network. A run turning passed or failed pops a herdr notification, and a failure also
    sends the owning conductor one line (notify(), or a stdout line for a non-herdr conductor), once per head
    commit — a later commit that is still red notifies again.
  • Quota lines carry each window's reset time (epoch seconds) when the source gives one (Claude, Codex, Antigravity,
    MiniMax, Copilot's monthly reset), as reset5h=/resetweek= fields that old cached lines (and anything without
    them) still parse fine. orq quota shows them as a human time ("resets 14:30", or weekday + time past today).
    orq pick --explain and its exit-3 message say when an agent out on quota comes back.
  • orq handoff: when a conductor's Claude account reaches conductor.handoff_at (default 85% of the 5h window, or the weekly limit), opens a new
    herdr space on an account with room, moves its issues and children's notices there and tells the new
    conductor to resume. Targets spread across accounts instead of always filling the lowest-usage one: it counts alive
    conductors per account first and picks the one with the fewest (then the lowest usage), skipping any at
    conductor.max_per_account (default 2). A move is skipped when every window over conductor.handoff_at (5h and/or
    weekly) resets within conductor.reset_grace_min (default 15) minutes, unless the quota reading is unreadable. It saves a
    trimmed recent transcript from the old pane as untrusted context
    for the new conductor; a failed read does not stop the move. It registers idle conductors
    doing PR/merge work. setup/orq-handoff.timer runs it every 5 minutes.
  • orq agent -R enforces policy.max_rounds: it counts follow-ups per session (whatever the prefix is called) and
    refuses the next with exit 4; -F overrides with the user's OK. /issue fixes the fix-<n> / review-<repo>-<n>
    names and limits visual validation (screenshots) to one cheap attempt.
  • orq claim records each conductor's name (its herdr workspace label, else ORQ_CONDUCTOR_ID), shows it in -l,
    and orq claim --from <name> [-f] finds (and takes over) a conductor's issues by any part of that name. /issue
    uses it when the user names another conductor, and resumes from .orquestra/<ID>/ instead of starting over.
    orq claim -l/--from and orq board now show the herdr workspace's current label while the pane is alive
    (it may have been renamed since the claim), falling back to the name stored at claim time.
  • orq pick review|opinion exits 2 with a clear message when more than one agent is eligible for the role (declared, not excluded or blocked, with a model for it; before quota checks) and
    neither --impl-agent nor --impl-vendor is given (--no-record/--explain do not change this): nothing to
    filter the reviewer down by otherwise.
  • agents.<name>.no_review: a regex that, when it matches the first line of a review tool's answer (or all of a short one) (e.g. revtool's "Nada para
    revisar"), ends that orq agent run status=fail instead of ok — "nothing was reviewed" is not a verdict, so
    orq pick's fallback and the conductor treat it as not run.
  • install.sh: orq-gc.service/orq-handoff.service now find node under mise and nvm. Their PATH always
    includes mise's shims directory (stable across versions); when node instead resolves to a version-specific
    directory (mise's activate PATH, or nvm, which has no static shims dir) the installer writes a drop-in with
    that real directory. A plain, system-package install is untouched either way.

Fixed

  • Multi-account orq pick: prefers an account whose pace does not project past the limit before falling back to lowest
    usage (when policy.pacing_penalty > 0), and keeps expired accounts with their fix command in the quota rejection note
    when the remaining accounts are over the limit.
  • Switching an agent's account no longer shows the old one's quota or block. The "last reading" quota cache is now
    tied to the login (Antigravity), and orq block records which login it was made for: when the agent or Claude
    account is logged into another one, the block is dropped on its own (claude, codex, antigravity, copilot, opencode).

Install: npm i -g @irythill/orq then orq setup.