Codex App GitHub connection for code review fails with `OAuth state invalid or not found`

What version of the Codex App are you using (From “About Codex” dialog)?

Unknown. Reproduced in the current Codex App build on March 20, 2026.

What subscription do you have?

ChatGPT pro

What platform is your computer?

macOS (exact platform string not available at the moment).

What issue are you seeing?

When I try to connect my GitHub account from the Codex App in order to enable GitHub code review, the OAuth flow fails and I get this error:

OAuth state invalid or not found

After the failure, the flow redirects me back to ChatGPT/GPT instead of completing the GitHub connection.

In a related permissions flow, clicking the GitHub permissions update link for my organization also led to a GitHub 404 page instead of a usable authorization/configuration page.

This prevents me from enabling Codex code review for my GitHub organization/repository.

What steps can reproduce the bug?

1. Open the Codex App.
2. Go to the GitHub connection / code review enablement flow.
3. Attempt to connect GitHub or update GitHub permissions for an organization.
4. Authenticate with GitHub.
5. Observe that the flow fails with:

OAuth state invalid or not found

1. The user is then redirected back to ChatGPT/GPT instead of returning to a completed GitHub connection state.

Additional notes about reproduction:

• Reproduces even in an incognito/private browser window.
• The issue is happening while trying to enable code review for a private GitHub organization/repository.
• Organization involved: semo-labs.

What is the expected behavior?

The GitHub OAuth flow should complete successfully, return control to the Codex App, and allow GitHub code review to be enabled for the selected organization/repository.

If the organization requires additional approval or permissions, the flow should surface a clear actionable message instead of failing with OAuth state invalid or not found or redirecting to an unrelated page.

Additional information

A few potentially relevant observations:

• This does not look like a simple browser cache issue because it still reproduces in incognito/private mode.
• There have been previous public reports of GitHub connector / Codex authentication issues, including OAuth state invalid or not found symptoms in related ChatGPT/GitHub flows.
• This may be specific to the Codex App GitHub connector state handling, organization approval handling, or the redirect/callback flow after GitHub authentication.

If useful, I can provide:

• exact timestamps of failed attempts,
• screenshots of the error and 404 page,
• the exact repository/org flow being used.