Codex Cloud auto code review: silent fail + dashboard shows quota available but review says limit reached

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #15274
• #14730
• #15405

Powered by Codex Action

Not a duplicate. This issue covers the full failure chain that none of the suggested issues address individually:

1. 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.

1. 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 (#15405) or caching (#14730).

1. 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.

I am seeing the same silent automatic-review failure.

Repository: private GitHub repository
Settings: Auto code review = Review my PRs; Review trigger = On PR open

Observed:

• Automatic review produced no comment, reaction, or review on multiple PRs.
• Manual @codex review works.
• Failure occurs on both codex/... and ordinary feature/... source branches.
• I removed and reinstalled the GitHub Codex integration; the issue persisted.

Latest reproduction:

• Non-draft PR, authored by me.
• No Codex activity more than 9 minutes after opening.

Seeing the same failure pattern on a ChatGPT Pro account with GitHub code review.

Context:

• Codex Cloud / GitHub PR review
• Subscription: Pro
• GitHub connector is connected to the correct GitHub account (bassings)
• Affected public PR: https://github.com/bassings/CouchPotatoServer/pull/109

Timeline observed today:

1. Initial @codex review request returned:

> You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

1. Codex dashboard for the same ChatGPT account showed available general/shared usage, not an exhausted state.
2. Disconnecting and reconnecting the GitHub connector changed behaviour: a fresh @codex review did run once and produced a real review finding on commit 3f011a98.
3. After fixing that finding and pushing commit 68fe80b7, another @codex review immediately 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:

• Per-repo last webhook received / last review attempted / last failure reason
• The exact account/workspace/quota bucket used by the GitHub app when posting a quota error
• A dashboard row specifically matching the GitHub bot’s “code reviews” quota decision
• A connector “resync” or health check instead of requiring disconnect/reconnect

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-connector comments on PRs:

“You have reached your Codex usage limits for code reviews.”

• Codex Analytics → Code review shows:

• 0 PRs reviewed
• 0 issues found
• no data for the period
• Codex Usage & billing shows:

• Pro plan
• General 5-hour usage limit: 93% left
• General weekly usage limit: 84% left
• GPT-5.3-Codex-Spark: 100% left
• 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:

• Uninstalled the Codex GitHub app.
• Revoked GitHub access.
• Reinstalled/re-authorized the Codex GitHub app.
• Removed and added back the relevant environments in Codex.

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.

Same issue here. ChatGPT Pro (20X) account.

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: https://github.com/openai/codex/discussions/8503

Exact same issue.

<img width="872" height="319" alt="Image" src="https://github.com/user-attachments/assets/4b353fc3-9d22-4397-a59e-09e53f337c7b" />

<img width="1035" height="468" alt="Image" src="https://github.com/user-attachments/assets/815773eb-443c-41ec-a181-ff3494129cb4" />
<img width="1032" height="555" alt="Image" src="https://github.com/user-attachments/assets/1107d0dc-f9e9-4068-b524-39349f1af47f" />

Adding another current reproduction from a ChatGPT Pro account with a deactivated legacy workspace in its account history.

Live state on 2026-07-09

• Active personal ChatGPT account: Pro
• Private organization repository is present in Codex Code Review settings
• Personal Auto review: on
• Repository setting: Review all PRs
• Trigger: Smart Trigger (Experimental)
• Enable credits use: on
• General usage dashboard: 96% of the 5-hour limit remaining and 99% of the weekly limit remaining
• Code review analytics: 0 PRs reviewed, 0 issues found, and no data for the period
• Credits remaining: 0
• A fresh manual @codex review on a PR authored by the connected GitHub user received the usage-limit response after 9 seconds
• The GitHub App installation is healthy: the connector receives the event and posts the failure response, with the expected repository and pull-request permissions

There 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:

1. Whether individual Pro currently includes any GitHub code-review allowance.
2. Which account/workspace/quota bucket the GitHub connector is evaluating.
3. Whether Support can clear a stale GitHub-to-workspace binding server-side.
4. Whether credits purchased on the active personal Pro account would definitely be used by this installation.

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.