GitHub connector “Connected” but unusable for private repos - OAuth token scope never applies

Coding with ChatGPT Codex CLI
1

I’ve had the GitHub connector linked for months now, and it shows as connected on both ends in ChatGPT desktop/web/mobile and GitHub. OAuth authorization succeeds, and I’ve tried both “All repositories” and “Specific repositories,” including re-installing multiple times.

Despite that, ChatGPT cannot list, search, or open any private repo files. It acts as if no repos exist at all.

I’ve confirmed:

  • GitHub → OpenAI OAuth app has repo and read:user scopes.

  • Connector status in ChatGPT is green and authenticated.

  • Reinstalling, relinking, clearing cookies, and switching browsers makes no difference.

This isn’t user error… it’s a backend regression where ChatGPT never receives a usable delegated token, even though the connection is active. Other users have reported the same issue: the connector “looks healthy” but effectively does nothing for private repos.

Please escalate this to the integration team responsible for the GitHub connector’s token proxy. It’s currently impossible to access private repos through ChatGPT even when fully authorized, defeating the point of the connector.

I’m on a paid ChatGPT plan, so this is a core advertised feature that needs a functional fix or at least an official acknowledgment.

1 Like
2

This isn’t much help probably, but what worked for me is removing it entirely from ChatGPT specifically (not Codex), disconnecting the app from my Github org, then reconnecting in ChatGPT, then lastly re-adding the app to the Github org. I tried disconnecting and reconnecting several times before this but htis is the only thing that worked.

3

Great idea, but I’ve been through every troubleshooting step i can find in every order I can find on both chatgpt and openai support, but both admit that it is a problem with their back-end after running through troubleshooting steps and even waiting for days (or months) between re-linking the connector from scratch every which way.

Hilariously the openai one told me that my issue was being escalated but has no memory in future visits to follow up and no communication (automated or not) from them about a resolution.

4

As of today (Nov 12, 2025), the ChatGPT Codex Connector seems to be utterly broken, because it isn’t using OAuth.

After connecting ChatGPT to Github, Github → settings → installations shows ChatGPT Codex Connector under Installed GitHub apps and Authorized GitHub apps tabs, but not under the Authorized OAuth Apps tab.

This effectively prevents the LLM for interacting with any private repositories.

The only two “solutions” are to either set the repository to public, or upload the files to the current conversation. Any code changes have to be made manually.

How to get unstuck connecting/disconnecting

If you’re unable to remove or add the connector, your cookies and/or local storage are likely the cause.

Do the following on both chatgpt and github:

  1. Log out
  2. Clear cookies and local storage.
    • In Firefox, click on the lock next to the URL and you’ll see an option to “Clear cookies and site data”.
  3. Log in again

You should now be able to add or remove your connectors. Note this won’t fix the OAuth issue.

1 Like
5

You can actually connect to private repositories as well. To do this:

  1. Log out.

  2. Clear cookies and local storage.

    • In Firefox, click the lock icon next to the URL, then choose “Clear cookies and site data.”

  3. Log in again.

  4. First, connect to any public repository in your GitHub account.

  5. Log in to GitHub.

  6. Add your private repository by following the steps in this video: How to Set Up ChatGPT Codex with GitHub (Step by Step + Live Demo).