GitHub @codex review is pinned to one workspace when the same repository is connected to two active workspaces

What issue are you seeing?

A single ChatGPT account belongs to two active workspaces. The same GitHub account and repository are connected in both workspaces, and Codex Code Review is enabled for the repository in both.

When a pull request comment triggers @codex review, the request is always routed to only one of the workspaces. If that workspace has exhausted its Code Review usage limit, the review fails even though the other connected, active workspace still has Code Review quota remaining.

There is no indication in GitHub showing which workspace received the request, and there is no supported way to select the intended workspace.

What steps can reproduce the bug?

1. Use one ChatGPT account that has access to two active workspaces.
2. Connect the same GitHub account and repository to Codex in both workspaces.
3. Enable Code Review for the repository in both workspaces.
4. Exhaust the Code Review allowance in the workspace that currently receives GitHub review requests, while leaving allowance available in the other workspace.
5. Add @codex review to a pull request.
6. Observe that the request continues to use the exhausted workspace and fails instead of using or offering the other eligible workspace.

Expected behavior

Codex should handle the ambiguous multi-workspace mapping explicitly. Any of the following would resolve the problem:

• Route the review to an eligible connected workspace with remaining Code Review quota.
• Allow the user to select the workspace for a repository or for an individual @codex review request.
• Display which workspace owns the GitHub Code Review mapping and provide a supported way to change it.
• If automatic failover is intentionally unsupported, return an actionable error identifying the selected workspace and explaining how to switch the repository mapping.

Actual behavior

• The same GitHub repository appears connected in both active workspaces.
• @codex review consistently routes to only one workspace.
• Exhaustion in that workspace blocks the review even when the other workspace has remaining quota.
• The GitHub response and Codex settings do not make the routing decision or workspace ownership clear.
• Disconnecting/reconnecting or changing settings is currently the only apparent way to influence routing, and the selection rule is undocumented.

Impact

Users with Personal and Business/Team workspaces, or multiple active organizational workspaces, can have paid Code Review capacity that is inaccessible from GitHub. The lack of visible workspace attribution also makes the usage-limit message misleading and difficult to troubleshoot.

Environment

• Product: Codex Cloud GitHub Code Review
• Trigger: @codex review
• Configuration: same ChatGPT account, two active workspaces, same GitHub account and repository connected in both
• Repository details omitted because the repository is private

Related issues

• #26867 — GitHub PR review remains associated with a deactivated workspace
• #31001 — GitHub Code Review reports a usage limit while the dashboard shows quota
• #15477 — Code Review quota/connector state mismatch

This report is specifically about ambiguous routing when two active workspaces both connect the same GitHub repository, and the inability to use or select the workspace that still has available Code Review quota.