Codex Cloud repository selector hides another organization's repositories when GitHub App access is set to All repositories

Summary

Codex Cloud's repository selector appears to drop repositories from one GitHub organization depending on how many repositories are exposed by another GitHub App installation.

This is reproducible by changing the ChatGPT Codex Connector repository access scope in GitHub. It looks like a repository discovery / pagination / result-cap issue rather than a GitHub permission problem.

Environment

• Codex Cloud / web repository selector
• GitHub App: ChatGPT Codex Connector
• Multiple GitHub App installations / organizations
• Affected organization: MonakaVR
• Example affected repository: MonakaVR/MonakaProtocol

GitHub-side permissions for the MonakaVR installation are valid, and Repository access is set to All repositories.

MonakaVR/MonakaProtocol itself exists and currently has multiple branches on GitHub (main and refactor/monaka-layer-separation).

Reproduction

1. Have the Codex Connector installed for at least two GitHub organizations/installations.
2. Keep the MonakaVR installation enabled for all repositories.
3. On another organization/install, set Repository access to All repositories (this organization has substantially more repositories).
4. Open the Codex Cloud repository dropdown.
5. MonakaVR repositories are missing from the dropdown.
6. Change the other organization/install from All repositories to Only select repositories and expose only one repository.
7. Re-open / refresh the Codex repository dropdown.
8. MonakaVR appears immediately in the dropdown.
9. Change the other organization/install back to All repositories.
10. Re-open / refresh the dropdown.
11. MonakaVR disappears again.

The appearance/disappearance follows the repository scope change immediately and reproducibly.

Expected behavior

All repositories accessible through all authorized GitHub App installations should remain discoverable/searchable in the Codex Cloud repository selector regardless of how many repositories another installation exposes.

Actual behavior

Increasing the accessible repository set for another installation causes MonakaVR repositories to disappear from the Codex Cloud selector. Reducing that installation to one selected repository makes MonakaVR reappear immediately.

Additional observations

• This does not look like an authorization issue on MonakaVR: the GitHub App is installed there with All repositories access and read/write permissions.
• The same repositories are accessible through GitHub itself/API; the problem is specifically the Codex Cloud repository discovery / dropdown.
• Before discovering this reproduction condition, Codex tasks created against the affected repo landed in an internal work branch snapshot where the expected remote branches/files were not visible, which is consistent with the wrong/incomplete repository snapshot being selected.
• Possible causes: repository result cap, missing pagination, cross-installation aggregation truncation, or local filtering over a truncated backend result set.

If useful, I can also collect the browser Network response for the repository search endpoint and determine whether the missing repositories are absent from the backend response or only omitted by the frontend dropdown.

Start with the Codex Cloud repository dropdown and capture the browser Network response for the repository search endpoint while changing GitHub App access scopes. Compare whether MonakaVR/MonakaProtocol is absent from the backend response or omitted by the frontend; done means all repositories from all authorized installations remain discoverable regardless of another installation's size.