Repository navigation
Codex Cloud auto code review: silent fail + dashboard shows quota available but review says limit reached #15477
Description
What variant of Codex are you using?
Codex Cloud (chatgpt.com/codex) — GitHub auto code review
What subscription do you have?
Pro
What platform is your computer?
macOS arm64 (Darwin 25.3.0)
What issue are you seeing?
Three bugs in one:
Bug 1: Silent failure with stale GitHub connector
Auto code review was enabled and configured correctly (auto review ON, "Review all PRs", trigger "On every push"), but PRs received zero review comments and zero error messages. No bot reaction, no 👀, nothing. Multiple PRs tested (#80, #81 on a private repo). The feature appeared to work in settings but silently did nothing.
Bug 2: Dashboard shows quota available but review says limit reached
The usage dashboard shows "Code review: 70% remaining (resets Mar 28)". But when actually triggering a review after fixing Bug 1, the response is "You have reached your Codex usage limits for code reviews." These two states directly contradict each other.
Bug 3: Disconnect/reconnect required to get ANY signal
The silent failure (Bug 1) was only resolved by disconnecting and reconnecting the GitHub connector in chatgpt.com/codex settings. After reconnect, at least an error message appeared (Bug 2). Before reconnect, there was zero indication anything was wrong.
Steps to reproduce
For Bug 1 (silent fail):
- Have a GitHub repo connected to Codex code review
- Enable auto review: "Review all PRs", trigger "On every push"
- Open PRs or push commits
- Observe: no review comments, no errors, no bot reactions
- Try
@codex reviewin PR comments — still nothing
For Bug 2 (quota mismatch):
- Check usage dashboard — shows ~70% code review quota remaining
- Disconnect and reconnect GitHub connector
- Trigger a review (PR open or
@codex review) - Receive "You have reached your Codex usage limits for code reviews"
- Check dashboard again — still shows quota available
Expected behavior
- If review cannot be triggered, show an error (not silent failure)
- Dashboard quota should match actual review eligibility
- GitHub connector state should not silently drift into a broken state
Actual behavior
- Reviews silently fail with no indication
- Dashboard shows 70% quota remaining while reviews are actually blocked
- Only disconnect/reconnect surfaces the (incorrect) error
Screenshots
Settings page shows: auto review ON, repo connected, "Review all PRs", "On every push"
Usage dashboard shows: Code review 70% remaining, resets Mar 28, 2026
Review response after reconnect: "You have reached your Codex usage limits for code reviews"
Related issues
- @ mentioning codex on PR's doesnt always trigger code reviews #13701 — @codex on PRs does not always trigger code reviews
- Codex App GitHub connection for code review fails with
OAuth state invalid or not found#15274 — GitHub connection OAuth state issues - To use Codex here, create a Codex account and connect to github #11881 — connector/account mismatch symptoms
- review is not working on some git issues #13185 — review not working on some git issues
- Failed to start code review #12316 — failed to start code review
- /review fails after long session and multiple retries #14077 — review interrupted loop
- Feature request: Limit Codex auto code review to default branch (or configurable branch allowlist) #13597 — branch filtering limitations
- Failed to create PR in Codex Cloud #14604 — Codex Cloud PR creation failures
Root cause hypothesis
- GitHub App installation state drifts silently — events stop being ingested but UI shows everything as configured
- Usage quota tracking is inconsistent between the dashboard display and the actual review eligibility check
- No observability: no "last event received", no "last review attempted", no failure reason per repo
Suggested improvements
- Add per-repo diagnostics in settings: last webhook received, last review task created, last failure reason
- Fix quota display to match actual eligibility
- Fail loudly on GitHub (bot comment or check status) when a review cannot start
- Add a "re-sync permissions" button instead of requiring full disconnect/reconnect
- Detect stale connector state proactively and notify users
Activity
github-actions commentedon Mar 22, 2026
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
OAuth state invalid or not found#15274Powered by Codex Action
AytuncYildizli commentedon Mar 23, 2026
Not a duplicate. This issue covers the full failure chain that none of the suggested issues address individually:
Silent connector drift — GitHub integration stops receiving events with zero indication. No error, no bot reaction, no failed check. The feature appears configured correctly in settings but silently does nothing. None of the linked issues cover this silent failure mode.
Quota display mismatch — Dashboard shows "70% remaining" while the actual review endpoint returns "usage limit reached." This is a separate data inconsistency bug, not just fast depletion (Possible quota/accounting issue: Pro weekly limit depletes unusually fast #15405) or caching (Usage still being cached when switching accounts in Codex App #14730).
Zero observability — No "last webhook received" timestamp, no "last review attempted" log, no failure reason per repo. The only way to discover the connector was broken was to disconnect and reconnect it manually.
The linked issues each touch one piece, but this is the only report documenting the end-to-end experience: a user with quota, with correct settings, getting absolute silence, and only discovering the real state after a manual reconnect that surfaces a contradictory error.
Happy to provide additional logs or screenshots if helpful.
RudiPersson commentedon May 26, 2026
I am seeing the same silent automatic-review failure.
Repository: private GitHub repository
Settings: Auto code review =
Review my PRs; Review trigger =On PR openObserved:
@codex reviewworks.codex/...and ordinaryfeature/...source branches.Latest reproduction:
bassings commentedon Jun 5, 2026
Seeing the same failure pattern on a ChatGPT Pro account with GitHub code review.
Context:
bassings)Timeline observed today:
@codex reviewrequest returned:@codex reviewdid run once and produced a real review finding on commit3f011a98.68fe80b7, another@codex reviewimmediately returned the same usage-limit message again.This does not look like a normal real quota exhaustion case from the user side. The connector can run a review after reconnect, then the quota error returns on the next request despite the dashboard not presenting an exhausted code-review state clearly enough to explain it.
The main product issue is the same as this report describes: GitHub review eligibility and the Codex dashboard/connector state disagree, and the user has no reliable way to tell whether the failure is quota, stale connector state, workspace/account mapping, or a backend accounting bug.
Useful diagnostics that would help:
hagelien commentedon Jun 14, 2026
Same issue here.
Codex GitHub code review appears to be blocked by a usage-limit check even though my visible quota is not exhausted.
What I see:
GitHub bot
chatgpt-codex-connectorcomments on PRs:“You have reached your Codex usage limits for code reviews.”
Codex Analytics → Code review shows:
Codex Usage & billing shows:
This has persisted for several days, despite no code reviews being completed.
Another interesting detail: Code review analytics shows zero activity going back months, even though I know Codex was reviewing PRs heavily before the past 1–2 weeks. So the analytics page itself also appears not to reflect actual historical code-review activity on my account/repo.
Things I have already tried, with no effect:
The issue still persists after all of this, so it does not seem to be fixed by reconnecting GitHub or recreating the Codex environment configuration.
rudrakshbhandari commentedon Jun 21, 2026
Same issue here. ChatGPT Pro (20X) account.
hagelien commentedon Jun 25, 2026
After more research, I think my problem is I used to have a business account which is now deactivated. Apparently Codex might try to use quota from that when reviewing code. More here: #8503
Tabberwocky commentedon Jul 1, 2026
Exact same issue.
james-lancelot commentedon Jul 9, 2026
Adding another current reproduction from a ChatGPT Pro account with a deactivated legacy workspace in its account history.
Live state on 2026-07-09
Review all PRsSmart Trigger (Experimental)Enable credits use: on@codex reviewon a PR authored by the connected GitHub user received the usage-limit response after 9 secondsThere is also a legacy/deactivated ChatGPT workspace associated with the account history. Earlier requests returned:
This workspace is deactivated. Select an active workspace and try again.Later requests changed to:
You have reached your Codex usage limits for code reviews.OpenAI Support previously summarized the problem as reviews routing to a deactivated workspace. The active Pro account's UI now shows no deactivated-workspace warning, but the GitHub connector does not expose which account, workspace, or quota bucket it is using.
The smallest one-time credits option currently shown in checkout is 1,000 credits for $40, so the only available diagnostic workaround requires nontrivial spend and may still route to the wrong workspace.
Could OpenAI clarify:
We are disabling automatic reviews for now to avoid posting a quota-error comment on every PR, and will retest after this issue has a confirmed fix or maintainer guidance.
assafkip commentedon Aug 3, 2026
Same failure, reproduced on 2026-08-03 with Codex CLI/Desktop 0.146.0 and a ChatGPT Plus account.
Backend state from
account/rateLimits/readat the same moment:rateLimitReachedType: nullhasCredits: truespendControlReached: falseObserved behavior:
codex execworkscodex cloud exectask is accepted, stays pending, then becomesERRORwith no diff@codex reviewimmediately says the code-review usage limit was reachedI uploaded a diagnostic bundle from the affected installation through
feedback/upload.Receipt:
no-active-thread-019fc964-c85b-7a63-8871-d11096ebac99Could OpenAI trace the receipt and confirm which ChatGPT account/workspace the GitHub connector resolves to? There is still no user-facing UI that exposes that binding.
assafkip commentedon Aug 3, 2026
Confirmed account-routing mismatch from Codex desktop logs.
Correct ChatGPT Plus account:
82e4557b-6b10-4cd3-b32e-8f58fc91e56dWorkspace still being resolved by the cloud surface:
108e5ab5-d7fc-43d3-a0f8-dd0551833be1The second workspace is explicitly logged as:
bannerType=workspace_owner_credits_depletedlimitReason=creditsThis explains the exact behavior:
Diagnostic upload receipt:
no-active-thread-019fc964-c85b-7a63-8871-d11096ebac99Requested fix: remove the stale connector binding to
108e5ab5-d7fc-43d3-a0f8-dd0551833be1and bind cloud tasks to82e4557b-6b10-4cd3-b32e-8f58fc91e56d.tom-takeru commentedon Sep 15, 2026
Summary
Since approximately September 14, 2026 UTC, Codex Cloud has stopped automatically starting code reviews for newly opened pull requests in a private GitHub repository.
Automatic reviews had worked reliably for approximately six months up to this incident, and no settings were changed.
Expected behavior
With personal Auto review enabled and the review trigger set to
On PR open, Codex should automatically react to and review a newly opened, non-draft pull request.Actual behavior
👀or👍), review task, review comment, or GitHub timeline event appears.@codex reviewstill starts and completes a review successfully.On PR openFollow personalFollow personalAction required — Update your GitHub permissions to enable code reviewsUpdatebutton leads to a 404 page.Steps to reproduce
@codex reviewas a comment; the manual review works.Update; it leads to a 404 page.Expected result
Automatic review should start when the pull request is opened, and the GitHub permission update flow should resolve successfully.
Could this be related to a regression in
pull_request.openedevent ingestion, a stale GitHub connector state, or a broken permission-update link?Update (September 16, 2026 UTC)
I performed an additional test on the affected private repository.
Review my PRsand the trigger set toOn PR open, a newly opened, non-draft pull request authored by me did not receive an automatic review.@codex reviewrequest on that pull request completed successfully.Review all PRs. The trigger remainedOn PR open.I also completed the GitHub organization Codex Connector authorization flow. The installation has access to all repositories and read/write access to pull requests. The Codex Code review settings page still displays the same permission warning.
No other repository-level code review settings were changed. I am leaving the repository set to
Review all PRsas a workaround.fix(pr-review): name a used-up usage limit when the review times out (#…
fix(pr): request a Codex review on each new PR again (#321)