GitHub connector appears connected but writes fail when Codex Connector is installed only on another accessible account

Summary

I was logged into my current GitHub owner account (<OWNER_ACCOUNT>), which owns the target repository.

From ChatGPT/Codex, I authorized ChatGPT Codex Connector with this account. The authorization completed successfully and ChatGPT showed GitHub as connected.

However, the flow ended immediately after authorization:

Login as <OWNER_ACCOUNT>
→ Authorize ChatGPT Codex Connector
→ Connected

There was no repository selection or GitHub App installation step.

Problem

Although I was authenticated as <OWNER_ACCOUNT>, the ChatGPT Codex Connector GitHub App was not installed on <OWNER_ACCOUNT>.

Instead, GitHub showed that the Connector already had an installation on an old collaborator account that my current account still had access to.

So the actual state was:

Authenticated GitHub user:
<OWNER_ACCOUNT> ✅

Target repository owner:
<OWNER_ACCOUNT> ✅

ChatGPT Codex Connector installation:
Old collaborator account ✅
<OWNER_ACCOUNT>            ❌

This caused confusing behavior:

• Repository reads worked.
• Repository metadata was accessible.
• Metadata could report push: true / admin: true.
• Actual connector writes failed with:

403 Resource not accessible by integration

The push/admin values represented the logged-in user's repository permissions, not whether the ChatGPT Codex Connector installation had write access to that repository.

Resolution

The issue was resolved by manually opening the ChatGPT Codex Connector GitHub App and installing it on the actual repository owner account:

https://github.com/apps/chatgpt-codex-connector

ChatGPT Codex Connector
→ Install
→ Select <OWNER_ACCOUNT>
→ Grant repository access
→ Save

After that, GitHub showed two separate Connector installations:

Old collaborator account
<OWNER_ACCOUNT>

The important fix was specifically installing ChatGPT Codex Connector on the repository owner account, not re-authorizing the GitHub user.

After the correct installation was present, connector write access worked.

Expected behavior

ChatGPT/Codex should clearly distinguish between:

1. GitHub user authorization.
2. ChatGPT Codex Connector GitHub App installation.
3. Repository access granted to that installation.

If the current user is authenticated but the target repository owner does not have a valid ChatGPT Codex Connector installation, the UI should detect this and direct the user to install/configure the Connector instead of appearing fully connected and later failing with:

403 Resource not accessible by integration

It would also help if user-level push/admin metadata were not interpreted as evidence that connector writes are available.