Note
This postmortem reflects a situation observed on July 13, 2026. The connector's behavior may change if OpenAI updates its GitHub integration.
I recently ran into an unexpected issue while trying to connect a new GitHub organization to the ChatGPT Codex Connector.
The bug will likely get fixed eventually, but I wanted to document it. This kind of incident is a good illustration of what can happen when a product evolves quickly.
The context
I wanted to authorize Codex to access a repo belonging to a new GitHub organization.
At the same time, ChatGPT's GitHub connector was transitioning to the new ChatGPT Codex Connector.
No way to tell if the two events were directly related. Either way, the observation was simple: adding the organization from the ChatGPT interface didn't work.
Without that authorization, Codex obviously couldn't access the repo in question.
The workaround
Instead of pushing on the ChatGPT side, I picked the process back up from GitHub.
Since permissions are managed through GitHub Apps, you can authorize the app directly from GitHub, without going through the ChatGPT interface.
The steps are simple:
- Open the GitHub organization's settings.
- Go to GitHub Apps.
- Install or authorize the ChatGPT Codex Connector.
- Select the repos to make accessible.
In my case, this immediately fixed the issue.
Direct link:
https://github.com/apps/chatgpt-codex-connector/installations/select_target
Takeaway
This postmortem is a good reminder of a useful principle.
When an authorization flow seems stuck in a third-party app, it doesn't necessarily mean the underlying service is unavailable.
In this specific case, the ChatGPT interface no longer seemed to properly support adding an organization. GitHub, however, kept handling its GitHub App permissions normally.
Before concluding a connector is broken, it can be worth checking whether the identity provider or origin platform lets you take back control.
That's exactly what got me unblocked.
Summary
If the ChatGPT Codex Connector won't let you add a GitHub organization, try authorizing directly from GitHub via GitHub Apps. Even as ChatGPT's interface evolves, permission management on GitHub's side generally keeps working.