AI Review

Limits and caps

Review caps, the 150-file ceiling, and what never counts.

The rolling caps

Two caps bound automatic reviews:

CapDefaultWindow
Reviews per pull request3Rolling 24 hours
Reviews per Workspace10Rolling 24 hours

The Workspace cap counts reviews across all tracked repos. When a PR would exceed either cap, Angada marks it skipped on the pull request. Manual re-runs still go through the cap checks.

GitHubPull request activity
AngadaReview and coordination
SlackLiving pull-request card
How the two caps interact

Flowchart: PR opened → debounce → cap check → review or skipped verdict.

The 150-file ceiling

Pull requests with more than 150 changed files are marked blocked instead of reviewed — enormous diffs produce shallow reviews, and Angada won't pretend otherwise. A manual re-run bypasses the ceiling when you genuinely want the monster reviewed, at the cost of a longer pass.

What never counts

Several things are excluded from reviews entirely, so they consume no cap:

  • Draft PRs — skipped until marked ready for review.
  • Bot-authored PRs — dependabot and friends are skipped outright.
  • The 90-second debounce window — a burst of pushes becomes one review, not five. The wait doesn't count as a review; the pass that follows does.

When you hit a cap

The PR shows skipped, and the next automatic review waits for room in the window. A manual re-run can help when the PR is eligible again, but it does not bypass either rolling cap.

Changing the caps

Settings → Review shows the review policy that applies to the Workspace. See Review settings for the controls currently available in the app.

On this page