GitHub Copilot: Request Code Reviews Through the REST and GraphQL APIs
GitHub CopilotGitHub Copilot code review can now be requested through the REST and GraphQL APIs, with an optional review effort level set per request. This lets teams start Copilot reviews from their own scripts, workflows, and internal tools. The feature is generally available to Copilot Pro, Pro+, Max, Business, and Enterprise plans, and the post also restates that Balanced is the default effort level.
Key Takeaways
- Copilot code review can now be triggered via REST and GraphQL APIs, so reviews can start from scripts, CI workflows, and internal tools.
- Each request can optionally set its own review effort level, matching review depth to the risk of the change.
- The feature is generally available on Copilot Pro, Pro+, Max, Business, and Enterprise plans.
- Balanced is the default effort level for new and existing repositories and organizations, effective September 28, 2026.
- Developers who explicitly chose Lite kept that setting, and they can switch back at enterprise, organization, repository, or personal level.
- Settings cascade, with each level able to override the one above, giving teams fine-grained control over review depth.
Sources & Mentions
1 external resource covering this update
Copilot Reviews From Your Own Tooling
GitHub Copilot code review can now be requested programmatically. GitHub added support for the supported REST and GraphQL APIs, so a review from Copilot can be triggered without opening the pull request page. When making a request, developers can optionally set the review effort level for that specific review.
The change brings Copilot code review into the systems teams already use. Scripts, workflows, and internal tools can now start reviews on their own schedule or in response to their own events, rather than depending on a manual request in the GitHub interface. The capability is generally available to Copilot Pro, Pro+, Max, Business, and Enterprise plans.
Choosing an Effort Level per Request
Each API request can carry its own effort level, so a script can ask for a light pass on a small change and a deeper pass on a risky one. This builds on the effort levels GitHub made generally available in August, where Lite suits straightforward changes and Balanced suits changes that warrant deeper analysis from a higher-reasoning model.
Balanced Remains the Default
The post also restates a change announced on August 28, 2026. The Default effort level now resolves to Balanced for new and existing repositories and organizations using Copilot code review, and this took effect on September 28, 2026. Anyone who had explicitly selected Lite kept that selection.
Developers who prefer Lite can change the level from Default to Lite wherever they manage it. Each level can override the one above it, from enterprise AI controls through organization and repository settings down to personal Copilot settings.