I ran into a surprisingly awkward GitHub connector problem: ChatGPT was connected to my personal GitHub space, but I also needed to work with repositories owned by several GitHub organizations. The personal repositories worked. The organization repositories did not appear to be available.
I disconnected and reconnected the connector, but that did not solve it. I removed the ChatGPT connector from GitHub Apps, uninstalled the GitHub plugin from ChatGPT, and started the setup again. This time I connected my personal GitHub account first, waited for that to succeed, then returned to the same connector installation page in the same browser session and selected one of my organizations. I repeated that process for the other organizations.
That worked. The useful part is that I did not try to create a second ChatGPT identity. I kept the same GitHub user connection and added the organizations as additional installations of the connector.
Important context
This is a practical workaround I tested, not an official OpenAI setup guarantee. The ChatGPT and GitHub interfaces may change, and your organization may require an owner to approve the GitHub App.
What was going wrong?
The normal ChatGPT reconnect flow made it feel as if I was reconnecting GitHub, but it only brought back the personal account I had already connected. It did not make the organization installations obvious. Reconnecting the same personal identity was not the same thing as granting the connector access to another repository owner.
The distinction became clearer after I found the OpenAI Community discussion “Connect a Personal GitHub Account and Multiple Organizations to ChatGPT, Codex (and Claude)”. That post explains the model well: one GitHub login can be associated with repositories under several owners, while the ChatGPT Codex Connector GitHub App needs an installation for each owner.
The workaround that worked for me
- Disconnect the GitHub connector from ChatGPT.
- Open GitHub’s installed applications and remove the ChatGPT connector installation if the existing installation is stuck on the wrong owner.
- In ChatGPT, remove or uninstall the GitHub plugin/connector integration if it is still present in the old state.
- Reconnect GitHub from ChatGPT and choose your personal GitHub account first.
- Complete the personal-account connection and confirm that it succeeds.
- Return to the same connector installation page using the previous page in your browser history. Keep the same browser session and GitHub login active.
- Select one of your GitHub organizations instead of your personal account.
- Install or request the connector for that organization, depending on your organization permissions.
- Go back to the same installation page again and repeat the organization step for every other organization you need.
The key moment is step six. After the personal connection succeeds, go back to the connector’s installation flow and choose an organization there. Do not expect the regular ChatGPT Disconnect and Connect buttons to present a clear “add another organization” workflow.
The more direct installation URL
The Community post also documents a more direct method: open the GitHub App’s new-installation page, select an owner, finish the installation, and open the page again for the next owner. The URL shown in that post is:
https://github.com/apps/chatgpt-codex-connector/installations/new
Use the personal account once, then open the same page again for each organization. This is probably the cleaner route when it works for your account. My reconnect-and-go-back flow was the workaround I discovered after the ordinary connector flow failed to expose my organizations.
How to check that it worked
- Confirm the personal repositories are still available.
- Search for a known private repository from each organization.
- Check GitHub’s installed applications and look for a separate installation for each repository owner.
- Give ChatGPT time to synchronize repositories after changing access.
- Test one small repository request from each organization before asking for a complete inventory.
If an organization uses approval rules or SSO, the connector may still need an organization owner to approve it. A missing approval is different from the connector simply never showing the organization in the installation flow.
Why this feels like a hack
The setup is not difficult because GitHub organizations are conceptually complicated. It is difficult because one ChatGPT connection, one GitHub identity, and several GitHub App installations are presented as if they were one setting. The interface should make it obvious that a personal account and multiple organizations can be added as separate repository-owner installations.
Until that becomes clearer, this is the sequence that worked for me: connect the personal account first, return to the installation flow in the same session, choose each organization one at a time, and verify the repositories afterward.
Have you found a cleaner way to manage several GitHub organizations with ChatGPT, Codex, or another GitHub connector? The Community thread linked above is a useful place to compare what works as these integrations change.