Repository navigation
v0.7.0
Added
- Docs in sync with 0.7.0 (both READMEs, the
/issueskill, troubleshooting):orq pick's new filters, conductor session names, orq fetching/committing for agents that can't,orq <command>instead of the oldorq-*names; the Portuguese README's config example caught up. Dependabot PR titles are explicit Conventional Commits. - Release automation: every push to
devopens or updates thedev → mainPR with the version the commits call for; aversioncheck fails a PR intomainuntil package.json and both changelogs carry it; merging intomaintags, publishes to npm and creates the GitHub release. PR titles must be Conventional Commits (see CONTRIBUTING.md). - Agent capabilities
commitandnetwork([agents.<name>], default true). For a write run in a git repo, orq does
what the agent can't:commit = false→ orq commits the changes after the run (message from aCommit: ...line in
the answer, else the title) and reports it under## Commit (by orq);network = false→ orq runsgit fetch origin
before the run so the agent can rebase locally. The prompt says so, so the agent doesn't try. Built in: antigravity
commit = false, codexnetwork = false. - Agent capability
base_commit(default: true if the agent takes the prompt, false for a tool that ignores it). A tool that diffs against
origin/<base>itself can't review-b <round-n.sha>, soorq pick review --base <ref>skips it when the base is a
commit, andorq agent -b <commit>falls back to the branch base (--base-branch <branch>, elseorigin/HEAD), warns and
adds## Review scope (by orq)to the answer: the review covers the whole branch, not just the round delta (#76).
Changed
- Node 22 or newer is required (
engines >=22). Node 20 reached end of life in April 2026. CI tests Node 22, 24
and 26.
Fixed
orq statsnames every agent and model: from the job's argv, then the pick, then the log (review tools run as plain CLIs no longer show as?; a-minside a prompt is no longer read as the model; opencode's screen model comes from its config). Time on a screen run stops at the first turn (<prefix>.turns), so a screen left open no longer inflates it; killed runs and older screen runs are left out of the time median (-). opencode tokens are counted again on its newer event format (#59).orq pickskips an agent whose CLI doesn't resolve on PATH (e.g. installed under another Node version), with a reinstall hint, instead of failing after dispatch (#77).- Several conductors on one workspace get distinct session names,
conductor-<workspace>:<herdr label or ORQ_CONDUCTOR_ID>, so they can address each other;orq claim -lends each line with thatsession=(#79). orq agent -Twith Codex sometimes never signalled the end of a turn (#62): a.idleft on the prefix by an earlier
run (another agent or session) made--turn codexdrop every real turn as a side thread. A new launch now clears it
(-Rwrites the resumed session). On herdr, a turn whose hook still doesn't fire (screen seen busy, then idle for
60 s,.donenot rewritten) is signalled by the runner asstatus=fail reason=no-hook, with the screen's last lines
as the answer.policy.max_roundscounts only review rounds:orq agent -R --reason verify|unblock(defaultreview) neither
counts nor is refused; every follow-up goes to.rounds-<session>.logandorq roundsshows them per reason. The
round is counted at launch, so a dispatch refused later costs none./issuenames verify fixesverify-fix-<n>.md(#75).- A review (
orq agent -ron areview*prefix) that exits 0 without a verdict ("I'll start by exploring the repo...")
is nowstatus=fail reason=no-verdictinstead ofok. A verdict = a finding with a severity or an explicit approval
(APPROVED, LGTM, aprovado, no findings...).policy.review_verdict = falseturns it off. Findings written as bare
[blocker] file:linelines (no list marker) now count, fororq roundstoo (#78). - Fix-round reviews converge on large branches:
orq agent -b <commit>attaches only<commit>..HEAD(a review tool
gets the round's start as{base}, not the whole branch again); in/issuea finding outside the fix diff never
opens a round, it goes to a deferred list (security/personal-data leaks stop and ask the user);orq roundswarns
freshwhen two fix rounds bring new heavy findings — split the issue (#72).
Install: npm i -g @irythill/orq then orq setup.