Codex GitHub code review reports usage-limit exhausted while linked dashboard shows available quota and zero review activity

Summary

Codex GitHub code review is blocking @codex review requests with a usage-limit error, but the linked Codex Analytics dashboard does not show any exhausted limit and the Code review analytics tab reports zero review activity.

This makes the error non-actionable and appears internally inconsistent: either the limiter is reading a hidden/incorrect quota bucket, analytics are not recording GitHub code-review usage, or the error links to the wrong dashboard.

Observed behavior

A GitHub PR comment with @codex review receives this bot response:

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

The linked dashboard at chatgpt.com/codex/cloud/settings/analytics shows visible plan meters with remaining usage, for example:

• 5 hour usage limit: 100% remaining
• Weekly usage limit: 98% remaining
• GPT-5.3-Codex-Spark 5 hour usage limit: 100% remaining
• GPT-5.3-Codex-Spark weekly usage limit: 100% remaining

The Code review tab on the same Analytics page reports no code-review activity:

• Issues found: 0
• PRs reviewed: 0
• No data for the selected period

This is inconsistent with active Codex review usage in GitHub over the same period.

Expected behavior

One of these should be true:

1. If the visible usage limits are not exhausted, @codex review should run.
2. If a separate GitHub code-review quota exists, the linked dashboard should show that quota, its current usage, and reset time.
3. If analytics are not real-time, the error should still expose the actual exhausted bucket or link to a page that does.
4. The Code review analytics tab should reflect GitHub code-review activity for the selected period.

Actual behavior

@codex review is blocked as over-limit, while the linked dashboard shows available quota and the Code review tab shows zero activity.

Impact

This blocks automated PR reviews and provides no actionable way to determine the real exhausted limit, reset time, or whether this is an account/workspace configuration issue.

Request

Please investigate whether:

• the GitHub code-review limiter is reading the wrong or hidden quota bucket,
• the Analytics Code review tab is not recording GitHub code-review activity,
• the error message links to the wrong dashboard,
• or there is an undocumented code-review-specific limit that is not exposed in the UI.

Screenshots are available showing the GitHub bot error, the Usage tab with remaining quota, and the Code review tab showing zero activity.