Check How the Balanced Default Applies When You Request Copilot Code Review by API
This page contains Coupang Partners affiliate links; the operator may earn a commission.
Key Takeaway
Requesting Copilot code review by API with the effort level at Default applies Balanced. GitHub announced REST and GraphQL support and per-request effort levels on October 2, 2026; explicit Lite stays.

Which plans get API support?
The GitHub changelog post lists Pro, Pro+, Max, Business, and Enterprise. From internal scripts or work tools you can start a review and set the effort level per request. The API permission to request a review and the permission to merge into a repository are separate, so look at them separately.
How do I choose between Lite and Balanced?
The official configuration documentation describes them as follows.
| Effort level | What the documentation says |
|---|---|
| Lite | Standard review |
| Balanced | Deeper analysis of complex logic, security-related code, and cross-service changes |
| Max | Marked as coming later, not yet available |
The documentation was checked on 2026-10-10. It says Balanced uses more AI credits and may add a little GitHub Actions time. The announcement has no figures that guarantee review quality or turnaround for every change. Read it only as a rough guide: repositories with frequent complex logic or security-related changes are candidates for Balanced, and repositories with many light changes are candidates for Lite.
Where do I check team and personal settings?
Code review settings exist at the enterprise, organization, repository, and personal levels, and the changelog post explains that each level can override the one above it. Before you automate requests from a work tool, first check which setting applies. Writing down both the API request option and the admin screen default makes it easier to compare unexpected credit use.
What do I decide when using automatic review and API requests together?
Enabling automatic review and the effort level are independent settings. Even if you turn off automatic review, the effort level stays and applies to manual requests. So decide at which point you want to request a review, whether on PR creation, a new commit, or completion of a particular check, and verify the run conditions so unnecessary requests are not repeated for the same change. Also keep the procedure for judging whether findings are resolved after you receive the results in your existing development flow.
Frequently Asked Questions
Do repositories that already chose Lite switch to Balanced?
The GitHub announcement says settings where Lite was explicitly chosen are kept. Balanced applies to new and existing repositories and organizations that use Default.
Can I choose the Max effort level now?
The official configuration documentation, checked 2026-10-10, shows Max marked Coming soon and says it is not yet available.
If I turn off automatic review, does the effort level go away too?
The official documentation says the two settings are independent. Even if you turn off automatic review, the effort level stays and applies to reviews you request manually.
Sources & Verification Date
- Copilot code review: API support and new default effort level (2026-10-02) · Verified
- Configuring code review by GitHub Copilot · Verified
All materials have been verified from official announcements and may have changed since verification.