What issue are you seeing?
GitHub integration environment resolution appears to fail only for non-review @codex comments.
In a private GitHub repo with Codex configured:
@codex review works on the same PR / code review path works.- Direct Codex Cloud task creation against the repo environment works and reaches
READY with no diff.
- The GitHub App installation is scoped to the repo, and Codex settings show the repo enabled.
- A non-review PR comment such as
@codex fix the suggested changes or @codex inspect the current PR context... receives this bot reply instead:
To use Codex here, create an environment for this repo.
This appears inconsistent with the GitHub integration docs, which say non-review @codex comments should start a cloud task using the pull request as context. I can provide exact repo, environment, task, and GitHub comment IDs privately; avoiding posting those on a public issue.
What steps can reproduce the bug?
- Set up a Codex Cloud environment for a private GitHub repository.
- Enable Codex code review for that repository.
- Confirm direct Cloud task creation against the environment works.
- Confirm
@codex review works on a PR in the same repo.
- On the same PR, post a non-review comment such as
@codex inspect the current PR context and report whether you can attach to the Codex cloud environment. Do not modify files, create commits, or push changes.
- Observe the bot reply:
To use Codex here, create an environment for this repo.
- Reinstall the ChatGPT Codex Connector GitHub App, create a fresh post-reinstall environment for the repo, delete older duplicate environments, and retest. The same bot reply still appears.
What is the expected behavior?
A non-review @codex comment on a PR should start a Codex Cloud task using the PR as context, or report the real blocker. It should not say to create an environment when a runnable environment for the repo exists and direct Cloud tasks can bind to it.
Additional information
This seems specific to the GitHub non-review task trigger resolver. The review path and direct Cloud task path both work.
Docs reference: https://developers.openai.com/codex/integrations/github#give-codex-other-tasks
What issue are you seeing?
GitHub integration environment resolution appears to fail only for non-review
@codexcomments.In a private GitHub repo with Codex configured:
@codex reviewworks on the same PR / code review path works.READYwith no diff.@codex fix the suggested changesor@codex inspect the current PR context...receives this bot reply instead:This appears inconsistent with the GitHub integration docs, which say non-
review@codexcomments should start a cloud task using the pull request as context. I can provide exact repo, environment, task, and GitHub comment IDs privately; avoiding posting those on a public issue.What steps can reproduce the bug?
@codex reviewworks on a PR in the same repo.@codex inspect the current PR context and report whether you can attach to the Codex cloud environment. Do not modify files, create commits, or push changes.To use Codex here, create an environment for this repo.What is the expected behavior?
A non-review
@codexcomment on a PR should start a Codex Cloud task using the PR as context, or report the real blocker. It should not say to create an environment when a runnable environment for the repo exists and direct Cloud tasks can bind to it.Additional information
This seems specific to the GitHub non-review task trigger resolver. The review path and direct Cloud task path both work.
Docs reference: https://developers.openai.com/codex/integrations/github#give-codex-other-tasks