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.
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.
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.
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:
Log out
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”.
Log in again
You should now be able to add or remove your connectors. Note this won’t fix the OAuth issue.
Is this something you’ve done recently? Because currently public repos can’t be connected to either, beyond reading them publicly by URL. No OAuth token means no connection to any repo.
Yes. I did it on 11/13 and yesterday I added another private repository . You are not going to see ChatGPT Codex Connector on the Authorized OAuth Apps, but you will be able to connect to the GitHub repository from Codex.
I’ve had the exact same issue as well. This is very strange because this feature used to work! Codex still connects, but I cannot query my private repos from the chat.
This is one of my main use cases for a Pro subscription. This is also more critical now as Codex doesn’t give good answers to simple queries or conceptual questions.
Even more perplexing - in some chats I have been recently able to access private repos and ask questions in ‘Thinking’ and ‘Pro’ 5.2 by passing the main URL. In other chats, it refuses to work. I’ve found that by initializing a chat with some coaxing I can get it to form the connection usually. Why this happens is beyond me - but clearly some of the tools it defaults to are not operable at the moment.
I’m having a similar (or possibly the same) issue despite exhaustive troubleshooting: all the steps above - disconnecting from git and gpt, clearing cookies, reconnecting, trying older models and deep thinking etc.. I’m always told some version of “GitHub connector tools are not present in the tool surface I can invoke”. Can you tell us what you said to get it to form the connection?
We can confirm that the behavior you’re encountering is a known issue that is already on our Engineering team’s radar and currently under active review.
As a temporary workaround, you can try the following:
Start a completely new chat and re-select the GitHub app before sending any messages
Remove and re-add the GitHub integration from both ChatGPT and GitHub, then open a new session
Avoid loading previous chats that may not correctly initialize tool availability
If available, try using ChatGPT on a different client (Web → Desktop app → Mobile) to force a fresh tool initialization
I tried these steps but had no luck. If anyone gets it to work, please let us know what you did.
I am experiencing the same issue. The above steps did not fix the issue. The odd thing is that my Github admin can see repos when he goes to Codex on the web. I can also connect to codex in the VS Code extension and it works fine. It’s just the web version that has some permission issue getting repos even though everything looks connected. Maybe there is a missing permission on the GitHub side?