GitHub @codex review stuck on deactivated workspace after reinstalling GitHub App and recreating environment

Open 💬 3 comments Opened Jun 8, 2026 by Eddie-RS

What issue are you seeing?

GitHub @codex review is stuck on a deactivated workspace for a private repository, even after reinstalling the ChatGPT Codex Connector GitHub App and recreating/confirming the Codex Cloud environment.

On multiple PRs in the same private repository, commenting:

@codex review

returns:

Codex Review: Something went wrong. Try again later by commenting "@codex review".

This workspace is deactivated. Select an active workspace and try again.

This appears to be a stale server-side workspace mapping for the GitHub @codex bot, not a repository permission or environment setup problem.

What I have already verified

  • The GitHub App is installed for the repository.
  • The GitHub App installation was reinstalled/recreated, resulting in a new installation ID.
  • The Codex Cloud environment exists for the same repository.
  • A fresh/current Codex environment was created/confirmed after reinstalling the GitHub App.
  • Direct Codex Cloud tasks can run against the environment.
  • ChatGPT GitHub Connector can read the same PR diffs successfully.
  • MFA is enabled.
  • Codex desktop OAuth was refreshed/re-logged-in after an OAuth expiry; the desktop app recovered, but GitHub @codex comments still fail.
  • Waiting after reinstall/reconnect did not resolve the GitHub bot error.

Expected behavior

GitHub @codex review should use the active ChatGPT/Codex workspace and the repository's current Codex environment, or provide a request ID/actionable diagnostic if the workspace cannot be resolved.

Actual behavior

GitHub @codex review continues to resolve to a deactivated workspace and fails before starting review.

Why this matters

This blocks the Codex GitHub PR review workflow for the repository. Since the direct Codex Cloud path and the ChatGPT GitHub Connector path both work, the failure seems isolated to the GitHub @codex bot's workspace/environment resolver.

Related public reports

This seems related to existing reports about GitHub environment resolution and deactivated workspace stale auth/state:

  • openai/codex#20093
  • openai/codex#19075
  • openai/codex#20168
  • discussion [#8503](<https://github.com/openai/codex/issues/8503>)

Additional information

I can provide exact private repository, GitHub App installation ID, Codex environment ID, PR URLs, and timestamps privately to OpenAI maintainers/support. I am intentionally not posting account/workspace identifiers publicly.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗