GitHub connector authenticates successfully but cannot access authorized repositories or PR review threads

Version of the Codex App
26.707.9981.0

subscription
Plus

Platform
Windows

Hello,

I am experiencing an authorization problem with the GitHub connector in Codex
Desktop. I observe the same issue in ChatGPT.

Environment:

• Codex Desktop version: 26.707.9981.0
• GitHub plugin version: 0.1.8-2841cf9749ae
• Operating system: Windows

For privacy reasons, I have redacted my GitHub username and repository name from
this public report. I can provide those details privately to the support team if
required.

Problem:
The GitHub connector successfully identifies my authenticated GitHub account,
but it cannot access any GitHub App installations, installed accounts, or
repositories.

Observed connector results:

• get_user_login succeeds and returns the expected authenticated account.
• list_installations returns an empty list.
• list_installed_accounts returns an empty list.
• list_repositories returns an empty list.
• get_repo for the expected repository returns 404 Not Found.
• Searching for my pull requests in that repository returns 422 Unprocessable

Entity. The response states that the repository cannot be searched because it
does not exist or the authenticated integration does not have permission to
access it.

Impact:
Codex cannot retrieve pull requests or inline review threads from the
repository. Therefore, it cannot use reply_to_review_comment to reply inside a
pull-request review thread.

Expected behavior:
After connecting my GitHub account and granting access to the repository, the
connector should:

1. Detect the GitHub App installation associated with my account.
2. List the authorized repository as accessible.
3. Retrieve its pull requests and review threads.
4. Post a reply to the top-level inline review comment of a thread.

No GitHub write operation was completed because the connector could not access
the repository.

How Codex attempts to access the repository:

There are two separate access paths:

1. Local Git access

Codex is running inside a local checkout of the repository on Windows. I have
confirmed that the expected GitHub repository is configured as its local Git
remote.

This local Git configuration only identifies the repository. It does not
grant the Codex GitHub connector access to GitHub.

1. GitHub connector access

To read or write GitHub data, Codex uses the installed GitHub plugin and its
separate GitHub App authorization. It does not use credentials from the local
Git remote.

Codex attempts to access the repository through the connector using its full
owner/repository name. The diagnostic sequence is:

• get_user_login succeeds and returns the expected account.
• list_installations returns an empty list.
• list_installed_accounts returns an empty list.
• list_repositories returns an empty list.
• get_repo returns 404 Not Found.
• get_users_recent_prs_in_repo returns 422 Unprocessable Entity because the

integration cannot search or access the repository.

To reply inside a pull-request review thread, Codex would then call
reply_to_review_comment with:

• The full repository name.
• The pull-request number.
• The numeric ID of the thread's top-level inline review comment.
• The reply text.

This write operation cannot be attempted because the connector cannot first
access the repository, pull request, or review comment.

This indicates that the local repository is correctly identified, but the
separate GitHub App authorization used by the connector is not providing access
to the authorized repository.

Could you please investigate whether:

• The GitHub App installation is correctly associated with my Codex/ChatGPT

account.

• The connector authorization has the required repository permissions.
• There is a stale or broken account-to-installation mapping in the connector

backend.

• Removing and reinstalling or reauthorizing the GitHub App is required.
• Additional diagnostic identifiers are needed from me through a private support

channel.

Thank you.

What steps can reproduce the bug?

Steps to reproduce:

1. Open Codex Desktop or ChatGPT with the GitHub connector enabled.
2. Connect and authenticate a GitHub account.
3. Authorize the GitHub App to access at least one repository.
4. Open a Codex task from a local checkout of an authorized GitHub repository.
5. Ask Codex to retrieve the repository metadata, pull requests, or review

threads through the GitHub connector.

1. Ask Codex to reply to an existing inline pull-request review thread.
2. Observe that get_user_login identifies the expected authenticated account,

but:

• list_installations returns an empty list.
• list_installed_accounts returns an empty list.
• list_repositories returns an empty list.
• get_repo returns 404 Not Found.
• get_users_recent_prs_in_repo returns 422 Unprocessable Entity.

1. Because the connector cannot retrieve the repository, pull request, or

top-level review comment ID, reply_to_review_comment cannot be executed.

Reproducibility:
The problem persists after starting a new conversation and reconnecting the
GitHub connector.

What is the expected behavior?

After connecting my GitHub account and granting access to the repository, the
connector should:

1. Detect the GitHub App installation associated with my account.
2. List the authorized repository as accessible.
3. Retrieve its pull requests and review threads.
4. Post a reply to the top-level inline review comment of a thread.

Additional information

_No response_