CodeRabbit posts a failing 'Review rate limit exceeded' commit status org-wide, making PRs UNSTABLE

[devantler]

🤖 Generated by the Daily AI Engineer

Problem

CodeRabbit is posting a failing commit status on PRs across the org when it is rate-limited:

context:     CodeRabbit
state:       failure
description: Review rate limit exceeded

Observed live on 5 open PRs across 4 repos (2026-07-14): platform#2584, platform#2629, ksail#6090, monorepo#2160, .github#96 — the oldest dating to 2026-07-13T21:30Z.

The consequence is a degraded merge lane, not just noise:

• Every affected PR's mergeStateStatus drops to UNSTABLE, because a non-required check is red.
• CI - Required Checks (the only required status check in the platform ruleset) is green on these PRs, so GitHub would still auto-merge them — but the red status makes them read as failing to any human or automated reviewer scanning the dashboard, and it blocks conservative auto-merge arming.
• It masks genuine failures: a real red check is indistinguishable at a glance from this rate-limit artifact.

Worth noting: automatic CodeRabbit review is disabled org-wide (2026-07-12), so CodeRabbit should not be reviewing on its own at all — yet it is still consuming rate limit and publishing failure statuses.

Proposed direction

This is a CodeRabbit-side (SaaS) setting, so it needs the maintainer — I have no access to it. Options, roughly in order of preference:

1. Stop CodeRabbit publishing a commit status entirely (or make it neutral/skipped rather than failure when rate-limited). A rate limit is not a review verdict, and a non-required check should never be red for an infrastructure reason.
2. Confirm auto-review really is off for the org — the rate-limit consumption suggests something is still triggering reviews on PR events.
3. If the limit is genuinely being hit by legitimate on-demand @coderabbitai review requests, consider the plan tier — though the agent has already moved to the Codex review lane for the green-review gate, so demand should be low.

Rough size

XS on the settings side; no code change in this repo.

Filing here as the org-config home. Not shipping a .coderabbit.yaml — per-repo CodeRabbit overrides are explicitly maintainer-reserved.

[coderabbitai]

🔗 Related PRs

#74 - feat(rulesets): require the CodeRabbit review status check org-wide [merged]
#75 - revert(rulesets): drop the provider-uncreatable CodeRabbit required-check ruleset [merged]
#86 - fix: gate repository-permissions/ until provider-upjet-github supports shaPinningRequired [merged]
#88 - feat: archived-repo pattern + reusable-workflows archival groundwork [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[devantler]

🤖 Generated by the Daily AI Engineer

Escalating: this now blocks two lanes, not just the check display

New evidence from today (2026-07-14, ~14:35Z). The rate limit is no longer only a cosmetic red check — it is blocking delivery in two independent ways:

1. It stalls the bot-merge lane. The CodeRabbit failure status sits on PRs as a non-required check, which drives mergeStateStatus to UNSTABLE. Auto-merge then never completes. Currently affected: platform#2629 (dependabot setup-go bump) and platform#2633 — both otherwise check-green, zero threads, codex-green at head.

2. It deadlocks the green-review gate. Promotion requires ≥1 green review at head from CodeRabbit or Codex. On platform#2631 I switched to the CodeRabbit lane and got:

Review limit reached — @devantler, you've reached your PR review limit, so we couldn't start this review.

With the Codex lane non-converging on that PR for unrelated reasons, no green review is obtainable at all, so a ready, CI-green, threads-clear draft cannot be promoted. That PR closes a live privilege escalation, so the cost here is real.

What would fix it

This is a plan/quota condition on the CodeRabbit side, so it needs a maintainer decision rather than an agent change. Options, roughly in order of leverage:

• Raise the CodeRabbit plan/seat limit (removes both symptoms at once).
• Stop CodeRabbit from publishing a failure commit status when it is merely rate-limited — a rate-limit is not a review verdict, and reporting it as failure is what poisons mergeStateStatus. A neutral/skipped status would unblock symptom 1 immediately.
• Failing both: make the CodeRabbit status non-blocking for UNSTABLE purposes so bot PRs can auto-merge, and lean on Codex for the review gate.

I have deliberately not worked around this (no threshold-lowering, no check-disabling) — flagging it for a decision.

[devantler]

🤖 Generated by the Daily AI Engineer

Correction to my comment above — I overstated symptom 2

I claimed the rate limit "deadlocks the green-review gate" such that no green review is obtainable. That was wrong, and I want it corrected on the record before it misleads anyone.

Reading CodeRabbit's full refusal message shows it names its own refill window:

Review limit reached … Next review available in: 13 minutes

And CodeRabbit duly served ksail#6121 one minute later (14:35:53Z) with a real, valid finding. So the limit is a rolling, time-windowed quota on review starts that refills continuously — not an outage, not a per-PR cap, and not a deadlock. The correct handling is simply to retrigger after the stated window, which I have now done on platform#2631.

What remains genuinely actionable

Symptom 1 stands, and it is the real cost: CodeRabbit publishes a failure commit status (Review rate limit exceeded) when it is merely rate-limited. A quota state is not a review verdict, but as a failure status it drops PRs to mergeStateStatus: UNSTABLE, which stalls the trusted-bot auto-merge lane (currently platform#2629, platform#2633 — both otherwise check-green with zero threads).

So the ask narrows to:

• Have CodeRabbit emit a neutral/skipped status rather than failure when it is rate-limited (fixes the UNSTABLE stall directly), and/or
• Raise the plan limit so the quota is not hit in normal operation.

Apologies for the noise on the first pass — flagging the correction rather than quietly leaving it.