AI Review usage and limits
How active developers are counted, and where review caps fit in.
How "active developers" are counted
An active developer is a distinct GitHub login that authored or reviewed a tracked pull request in the trailing 30 days. The count is activity-based: someone who has left the team drops out of the count automatically, without anyone removing them.
On Free, the count is a hard cap. On Pro and Business, it's the boundary between tiers — see Subscription for the per-plan numbers.
Watching your usage
Settings → Usage shows your current active-developer count against your plan. Check it before renewal, or when the team grows.
Usage page with the active-developer count against the plan limit.
Usage limits versus review caps
Two different limits apply to AI review, and they live in different places:
| Limit | What it bounds | Where it's set |
|---|---|---|
| Active developers | Who gets reviews, per plan | Your plan — Subscription |
| Review caps | How many reviews run | Settings → Review — Limits and caps |
Hitting a review cap doesn't touch your billing; hitting your developer cap doesn't block reviews for those counted. The full cap rules are in Limits and caps.
Keeping the count honest
The count follows activity, so housekeeping mostly takes care of itself. Two things move it:
- A new teammate authors or reviews a tracked PR — they appear.
- A departed teammate's last qualifying PR ages past 30 days — they drop off.
Nothing needs manual cleanup, and reviewers who review without authoring count the same as authors.