Repository navigation
Onus v0.10.0
Track records that fill themselves in, and agents that work through Onus.
- Agents hand work in through MCP (ADR 0012,
onus help agents):onus mcpaddsonus_env_create,onus_env_run,onus_envs,onus_env_destroy,onus_evidence,onus_run_test,onus_submit,onus_judge,onus_escalate,onus_escalation,onus_lanesandonus_outcomes. Agents cannot record outcomes, grant escalations, mint tokens or choose their scope;--no-actionsleaves the tools out. Submissions are kept in.onus/submissions/and shown inonus ui; granted escalation tokens are kept beside their request for the agent to collect. - Outcome records kept by CI (ADR 0013,
onus help ci): withrecords: true, the GitHub Action classifies every pull request with its agent setup's track record, records the outcome when it closes and reverts when the default branch moves, all on anonus/recordsbranch of the repository. People record approvals, audits and incidents with/onus approve <row>,/onus audit ok|missand/onus incident <note> involved: …comments (write access only); an approval re-runs the check. The agent setup is read from anOnus-Agent:trailer, the branch name, the bot author or aCo-authored-bytrailer. Newonus ci pr|closed|comment|push|recordscommands do the work and run in any CI system. An incident now counts against its agent setup even after the change is reverted. - An outcomes dashboard in
onus ui: readsorigin/onus/recordswhen there is no local file, and shows changes by week and lane, each agent setup's progress toward auto-merge, and the pull requests in flight. - A better map in
onus ui: pan and zoom, a layout by folder beside the layers, focus on a component with one or two steps of neighbours, filters for imports, calls and types, a side panel for the selected component, and a treemap of the repository by folder and size.
Install
brew install onushq/tap/onus
curl -fsSL https://onushq.com/install.sh | shOr in a workflow: uses: onushq/onus/action@v0.10.0. Each archive is attested: gh attestation verify <archive> --repo onushq/onus.