Notable changes to @input-output-hk/agent-review and @input-output-hk/agent-review-pi. The two packages are versioned in lockstep.
- A new
agent-review initguided setup command: authenticates against GitHub, writes~/.agent-peer-review/config.json, bootstraps theai-reviewlabel profile on one or more repos, and prints a ready-to-paste MCP config snippet plus the orchestration skill's location. Accepts--repo(repeatable),--capture-metadata,--model,--agent,--tool-version, and--yesfor non-interactive use (for example, from an AI agent); falls back to interactive prompts when run from a terminal without--repo. - A new
AGENTS.mdat the repository root: a short, imperative install contract so an AI agent given the repo URL can install, authenticate, and configure the tool on its own.
- Opt-in, durable review metadata capture (
captureMetadataconfig field, default off). When enabled,completeandenrichappend a hidden, machine-readable footer to the review body, and the claim marker moves to a v2 shape that carriesmodel,agent, andtoolVersionalongside the existing fields. The footer recordsrole,verdict,machine,claimedAt, and whether the review posted after the head commit drifted. Off by default, so the workflow is unchanged unless you opt in.
findAgentPullsenumerates every pull request theai-reviewworkflow has touched, across open, closed, and merged states, not only the open oneslistsees. This is what backs the dashboard'ssync.PullRequestnow carriescreatedAt,updatedAt, andmergedAttimestamps.
- A new
~/.agent-peer-review/home directory holds per-user global config and state, overridable withAGENT_PEER_REVIEW_HOME.<home>/config.jsonis now the preferred config file location; the legacy~/.config/agent-review/config.jsonand./.agent-review.jsonlocations keep working. - Fixed an env-override bug where an environment variable that was set but empty (for example, a host that always exports it and leaves it blank) clobbered a config file value instead of falling through to it.
- The trigger label was renamed from
agenttoai-review. Re-label any existing pull requests that still carry the old label, and re-runagent-review labels bootstrapon every repository using the workflow.
- Raised the minimum supported Node.js version to 22.
- A local, unpublished
dashboardpackage now ships in the repo: asynccommand mirrors agent-reviewed pull requests into a local SQLite database, and aservecommand exposes that database as a read-only, localhost-only HTTP API and UI. See the docs for details.
First published release: an asynchronous AI-agent PR-review workflow over GitHub, usable from the CLI, an MCP server, and a pi.dev extension.
- All state lives on the pull request: an
ai-reviewtrigger label, native requested-reviewers for routing, a claim-marker comment that pins the head commit SHA, and a native PR review as the completion signal. No external queue, database, or long-running server. - A pure
corelibrary behind aGitHubGatewayport, with thin CLI, MCP, and pi.dev adapters over one code path. - Idempotent label bootstrap for the orthogonal label profile.
- Multiple requested reviewers run as a concurrent panel: the earliest to claim is the anchor and posts the single primary review; later claimants are enrichers that add one consolidated second opinion once the primary lands. Stale-anchor promotion cascades without deadlock, and a competing primary is guarded so exactly one primary is posted per round in normal operation.
- On claim, the task carries auto-detected per-language checklists, deepened domain skills (security and OWASP, cryptography, architecture), and the reviewed repository's own agent context (
AGENT.md,CLAUDE.md,.claude,.codex). All best-effort and bounded, and never able to fail a claim.
@input-output-hk/agent-review-pi: a native pi.dev extension registering the six review tools plus a skill, distributed as a Pi Package.
- Untrusted review context (the diff and the reviewed repo's own files) is fenced and labeled, with a served content policy that travels to every host. See
SECURITY.mdand ADR 0007. - Linear claim-marker parsing (no polynomial backtracking) and a least-privilege CI token.
- Published to GitHub Packages. See the ADRs under
docs/adr/for the load-bearing design decisions.