Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix GitHub non-review @codex comments report missing environment while direct cloud tasks and reviews work [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20093•Fetched 2026-04-29 06:23:04
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
GianniGabrielGianniGabriel
Participants
GianniGabrielGianniGabriel
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

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?

  1. Set up a Codex Cloud environment for a private GitHub repository.
  2. Enable Codex code review for that repository.
  3. Confirm direct Cloud task creation against the environment works.
  4. Confirm @codex review works on a PR in the same repo.
  5. 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.
  6. Observe the bot reply: To use Codex here, create an environment for this repo.
  7. 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

extent analysis

TL;DR

The issue may be resolved by re-examining the GitHub App installation scope and Codex environment configuration to ensure they are correctly set up for non-review comments.

Guidance

  • Verify that the GitHub App installation is correctly scoped to the repository and that the Codex environment is properly configured for non-review comments.
  • Check the documentation for any specific requirements or limitations for non-review comments, such as specific formatting or keywords.
  • Test non-review comments with different wording or formatting to see if the issue is specific to certain types of comments.
  • Consider providing the exact repo, environment, task, and GitHub comment IDs privately to the support team for further investigation.

Notes

The issue seems to be specific to the GitHub non-review task trigger resolver, and the review path and direct Cloud task path both work, which suggests that the problem may be related to the configuration or setup of the non-review comment trigger.

Recommendation

Apply workaround: Reinstall the ChatGPT Codex Connector GitHub App and recreate the environment for the repo, as this has been attempted before and may resolve the issue if the problem is related to the installation or configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix GitHub non-review @codex comments report missing environment while direct cloud tasks and reviews work [1 participants]