Chat GPT : Unable to connect GitHub Auth to OpenAI Codex (stucvk at Configuration Page)

Fixing the Infinite GitHub Configuration Redirect Loop in ChatGPT

If you’re trying to connect GitHub to OpenAI Codex inside ChatGPT and it keeps redirecting you back to the GitHub configuration page, you’re not alone.

Many users report the same frustrating loop:

• Click the Codex button in ChatGPT
• Go through onboarding
• Authorize GitHub
• Get redirected to GitHub App configuration
• Select account and repositories
• Redirect again
• Repeat endlessly

Codex never recognizes the authorization, even though GitHub shows it as installed.

This guide explains why it happens and the working fixes.

---

What’s Happening with GitHub to OpenAI Codex ?

The issue typically looks like this:

• GitHub authentication succeeds
• GitHub App appears installed
• Codex doesn’t detect connection
• You’re sent back to configure repositories again
• Sometimes you see:
  “Error with connector connection.”

In some cases, users are even prompted for a PIN they never set.

This is usually caused by:

• Broken OAuth session
• Cached authorization data
• Mismatch between GitHub App install and ChatGPT connector
• Corrupted cookies
• Empty repository (rare but confirmed issue)

---

Fix 1: Disconnect GitHub from ChatGPT and Reconnect

This is the most commonly successful solution.

Step-by-step:

1. Go to ChatGPT
2. Open Settings
3. Navigate to Connectors
4. Disconnect GitHub
5. Refresh the page
6. Go back to Settings → Connectors
7. Click GitHub and reconnect manually
8. Then retry connecting Codex

After reconnecting properly from the Connectors menu, Codex should recognize your repositories.

---

Fix 2: Revoke OpenAI from GitHub Directly

If reconnecting from ChatGPT doesn’t work, you need to reset from GitHub’s side.

Do this:

1. Go to GitHub
2. Open Settings
3. Navigate to Applications
4. Find the OpenAI / Codex App
5. Revoke access or uninstall it

Then:

6. Return to ChatGPT
7. Go to Settings → Connectors
8. Remove GitHub connector
9. Reconnect from scratch

This forces a clean OAuth handshake.

---

Fix 3: Clear Cookies and Log Out of Both Platforms

If the loop continues:

1. Log out of ChatGPT
2. Log out of GitHub
3. Clear browser cookies
4. Close browser completely
5. Reopen browser
6. Log into GitHub first
7. Then log into ChatGPT
8. Reconnect GitHub via Connectors

Many users report this fixes the redirect loop permanently.

---

Fix 4: Delete Codex Installation and Environments

Some users were only able to disconnect after:

• Deleting Codex installation from GitHub
• Removing Codex environments
• Logging out everywhere
• Clearing cookies

After a full reset, reconnecting worked.

---

Fix 5: Make Sure Your Repository Is Not Empty

This is a lesser-known issue.

If your GitHub repository is empty, Codex may fail during setup.

To fix:

• Commit at least one file to the repository
• Push it to GitHub
• Then try reconnecting Codex

Codex does not clearly state this requirement during onboarding.

---

Fix 6: Try a Different Browser

If authentication keeps redirecting:

• Try Chrome if using Firefox
• Try Firefox if using Chrome
• Disable browser extensions temporarily
• Avoid ad blockers during setup

Some extensions interfere with OAuth callbacks.

---

Why This Happens

The most likely causes are:

• OAuth token mismatch
• GitHub App installation tied to wrong organization
• Browser caching stale auth data
• Connector session not refreshing
• Incomplete GitHub permissions

When the handshake fails, GitHub keeps returning you to the configuration page because it thinks setup is incomplete.

---

If You See “Error with Connector Connection”

This error typically appears before authentication completes.

Possible reasons:

• GitHub already partially authorized
• Conflicting installations
• Expired token
• Organization permission mismatch

In most cases, a full revoke + reconnect resolves it.

---

When to Escalate

If none of the above works:

• Confirm your GitHub account is verified
• Ensure you have admin permissions on repositories
• Check if organization policies restrict third-party apps
• Contact OpenAI support

---

Summary of Working Fix

The most reliable solution is:

1. Revoke OpenAI/Codex from GitHub
2. Remove GitHub connector from ChatGPT
3. Clear cookies
4. Log out of both services
5. Reconnect via ChatGPT → Settings → Connectors
6. Ensure repository contains at least one committed file

After this, Codex should recognize your repositories properly.