Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cubic.dev/llms.txt

Use this file to discover all available pages before exploring further.

cubic measures GitHub PR AI review usage in reviewed lines — the changed lines of code cubic actually reviewed in completed PR reviews. Auto-generated files, binaries, vendored code, and anything matching your ignore patterns are discounted automatically and barely touch your quota. So a 30,000-line PR that’s mostly a regenerated lockfile counts as a small fraction of that. Each paid seat adds to a shared reviewed-line pool for your whole team.
PlanReviewed lines per seat per billing period
Trial20,000
Team (paid)40,000
Pro100,000
A 5-seat Pro team gets 5 × 100,000 = 500,000 reviewed lines per billing period, pooled across everyone. You can see your current usage, reset date, and a breakdown by review type, base branch, and repository in Settings → Usage when reviewed-line limits apply to your installation. The quota resets with your billing period, not a rolling 30-day window.

​
What is not included

The reviewed-line meter applies to GitHub PR AI reviews. Other cubic features use separate limits and do not consume this reviewed-line pool:
  • CLI/local reviews
  • Codebase reviews and daily scans
  • Wikis
  • cubic coding agents

​
When you run out

If your team uses its full reviewed-line capacity, new GitHub PR AI reviews pause until the next reset. Existing comments stay on PRs, and replying to cubic still works. Other features are unaffected by this reviewed-line quota because they have their own limits.

​
Tips to reduce usage

Use these ideas when you want to lower reviewed-line consumption without changing your plan. Most options live in AI review settings or cubic.yaml.
  • Disable automatic reviews for repositories where you only want cubic to review PRs manually. Choose the repository in AI review settings and turn off AI reviews, or set reviews.enabled: false in cubic.yaml.
  • Ignore specific files or directories that do not need AI review. Add file globs in AI review settings, or add them to reviews.ignore.files in cubic.yaml.
  • Skip non-default base branches when long-lived branches do not need review. Configure ignore patterns for base branches in AI review settings or reviews.ignore.base_branches in cubic.yaml.
  • Avoid unnecessary full reruns. Pushing commits triggers incremental reviews (only new lines count). Manually re-triggering with @cubic-dev-ai review this PR runs a full review again — use it deliberately.
  • Use PR label ignores for work-in-progress PRs. Add label patterns in AI review settings or reviews.ignore.pr_labels in cubic.yaml.
For example: 
reviews:
  enabled: true
  ignore:
    files:
      - 'dist/**'
      - 'generated/**'
      - '*.lock'
When a file matches your ignore patterns, cubic skips it during PR review, so it does not spend reviewed-line capacity on that file.

​
How to get more

​
FAQ

Genuine large refactors and monorepo-wide changes do count close to their full size. If recurring large PRs are coming from generated files or fixtures, add them to your ignore patterns in cubic.yaml.
Pushing new commits triggers an incremental review and only the new lines count. Manually re-triggering a review with @cubic-dev-ai review this PR runs a fresh review and counts again — so use it deliberately.
No. Reviewed-line usage is based on the changed lines of code cubic reviews, not how many comments cubic leaves. Changing sensitivity can make cubic more or less selective about the issues it reports, but it does not change how much code cubic reviews.To reduce reviewed-line usage, change when reviews run or which files cubic reviews. You can do that with AI review settings or cubic.yaml.
Yes. Add a PR label ignore pattern in AI review settings, or add the label to reviews.ignore.pr_labels in cubic.yaml. For example, you can ignore PRs labelled wip or skip-review until the label is removed.
No. Only completed reviews count toward your billing-period capacity. If you cancel a review, merge a PR before its review finishes, or cubic hits an error, those reviews don’t use any of your quota.
Public repositories can use cubic for open-source work at no cost, subject to separate reviewed-line fair-use and abuse-protection limits. These safeguards are designed for unusually large or high-volume usage, not normal OSS maintenance.For paid teams, eligible public-repository PRs from external contributors are handled separately from the team’s reviewed-line pool, so external OSS traffic does not spend capacity intended for private and internal work. Unpaid public repositories use the public fair-use pool instead of the private free-plan review count.If your open-source project is blocked and you think the limit was applied incorrectly, email contact@cubic.dev with your organisation, repository, and PR link.
Your cap recalculates immediately. Adding seats gives you more capacity right away; removing seats lowers it.
Ultrareview reviews the same lines as a normal review — just more thoroughly — so it counts the same against your reviewed-line capacity. It also has its own limit of 2 Ultrareviews per paid seat per billing period, pooled across your team.
Email contact@cubic.dev with your organisation name and we’ll dig in.