After adding Codex to my GitHub repo, granting it permission to review all repos, and submitting a PR, I’m not seeing where Codex is automatically review my PRs as advertised. Upon submitting a comment in the discussion section (@codex review), I get the following error: “To use Codex here, create a Codex account and connect to github.”
I have a ChatGPT Plus account and I’ve been able to use Codex locally via the IDE extension.
This is a strange error message because as of today there are no separate codex accounts. Instead Codex can be used with an API key or a ChatGPT subscription.
Can you confirm that you are using OpenAI Codex and not a third party app with a confusingly similar name?
Good suggestion. I’ve tried that and it yielded the same results, I’m afraid. Definitely hoping you guys solve this soon so I can look into cancelling my Cursor Bugbot subscription lol
I learned that pinging @ codex will actually work when the ChatGPT account is connected to the GitHub account. This needs to be done from inside ChatGPT → Settings → Connectors
The team also updated the description of the codex organization on GitHub. This organization is separate from the OpenAI organization and exists only to allow pinging @ codex on GitHub.
Great!
On my side I noted a prompt to confirm additional permissions required by the app. Most likely because I connected it shortly after the Codex GitHub app was released and there have been feature upgrades in the meantime.
The PR Review feature is tightly coupled with the Branch format input field in Settings > General (Codex web-app). It defaults to codex/{feature}. Rename it to your actual repo name (e.g., myrepo/{feature}).
Once saved, go to your open PR on GitHub and tag Codex in a new comment. It should respond with an eyes emoji, indicating Codex has started reviewing your PR.
Also, on the Connectors tab (Codex web-app), ensure the GitHub account associated with Codex is correct. Click the Settings button, go to GitHub, and verify your account has access to the necessary repos. The same applies to organization repos. You don’t need to configure granular repo access to get it working.