GitHub opened Copilot code-review requests to supported REST and GraphQL APIs on October 2, allowing internal tools and workflows to start a review without a person clicking the reviewer menu. The request can also carry an effort level, while Balanced is now the inherited default for repositories and organizations that did not explicitly choose Lite.
The release changes where review policy can be enforced. A platform team can initiate reviews from its own automation, but it must decide whether each request names an effort level or inherits an organization or repository setting.
API requests add an orchestration hook
GitHub says supported REST and GraphQL APIs can request a Copilot review and optionally set effort for that request. This makes it possible to trigger review from a release workflow, internal developer portal or compliance process rather than relying only on a pull-request author.
The useful boundary is narrow: the API starts the review. Automation still needs to record whether the request succeeded, associate the result with the pull request and decide what to do when comments arrive. Teams should avoid treating “request accepted” as equivalent to “review completed with no findings.”
Balanced now fills the inherited setting
GitHub changed the default review effort to Balanced on September 28, 2026 for new and existing repositories and organizations using Copilot code review. The company says an explicitly selected Lite setting was respected. In other words, the migration changes inherited behavior, not a deliberate Lite choice.
The distinction matters when review cost and latency are managed centrally. If an API request omits effort, the effective setting can come from organization or repository configuration. A deterministic workflow should either pass the intended level per request or verify the inherited setting during rollout.
GitHub’s interface describes Lite as an efficient, lower-cost pass and Balanced as deeper analysis at moderate cost. Max is shown as coming soon in the release image, so it should not be treated as a generally available option.
Availability and the remaining operational question
The API and effort changes are generally available on Copilot Pro, Pro+, Max, Business and Enterprise plans. Repository administrators can find the control under Settings → Copilot → Code review; organization owners use the corresponding organization settings path.
The main implementation question is not whether another automated reviewer can be launched. It is how that reviewer fits existing branch protection, human approval and queueing rules. GitHub’s announcement documents request initiation and effort selection, but does not supply a universal policy for making Copilot output merge-blocking. That remains a repository-governance decision.
GitHub has been expanding Copilot review in separate increments, including shell-tool access and multi-agent Lite reviews. The API release is the integration step: it lets teams place those reviews inside their own control plane instead of adding another manual action to every pull request.
