Features
PR Review
Review eligible pull requests and publish concrete merge-readiness evidence.
Review eligible open pull requests
PR Review runs for eligible open, non-draft pull requests on the configured cadence. It reads the diff and nearby code, checks validation context, publishes concrete findings, and records a separate merge-readiness summary.
Verified review artifact
A successful run must publish one verified review summary on the triggering pull request. Inline findings remain specific and actionable, while the summary records the overall result.
- Focus on correctness, security, regressions, and missing validation.
- Avoid restating the diff or adding low-value style commentary.
- Use repository instructions to define local review expectations.
Ephemeral review workspace
Pull-request-review runs use an ephemeral checkout. They fail if the agent changes the repository checkout because the role is intended to inspect and review, not implement.
Frequently asked questions
Are draft pull requests reviewed?
No. The current trigger targets eligible open, non-draft pull requests.
Can the review agent modify code?
The review role uses an ephemeral checkout and fails if it changes the repository checkout.
Does every review leave inline comments?
Not necessarily. It publishes concrete findings when present and records a verified review summary for the run.
Can I set repository-specific review instructions?
Yes. Add focused instructions in the PR Review agent configuration.
Do provider credentials reach the hosted website?
No. Provider API keys and OAuth roots remain in the local runner environment. The hosted control plane receives sanitized availability, model catalog metadata, job events, and outcome evidence.
Can agents in one repository use different models?
Yes. Each built-in or custom agent selects its own provider, catalog model, supported thinking level, and repository tool image.