GitHub @codex review silently dropped for one org after the App installation was recreated (no task is ever created)

GitHub @codex review silently dropped for one org after the App installation was recreated (no task is ever created)

Summary

@codex review on PRs in PowerNukkitX/PowerNukkitX produces nothing: no review, no comment, no 👀 reaction, and no task appears in chatgpt.com/codex at all. Another org on the same ChatGPT account (bedrock-v/Vedrock) works normally at the same minute with identical settings. The break started after the Codex GitHub App installation on the PowerNukkitX org was removed and reinstalled.

Timeline (UTC, 2026-09-19 unless stated)

Working period, same repo:

PR	trigger	Codex response
3206	09-13 20:27	issue comment 20:30
3199	09-13 20:38	PR review 20:43
3207	09-14 14:09	PR review 14:13
3213	09-14 17:27	PR review 17:35
3218	09-15 17:18	task ran, review 17:42

Broken period:

• 17:15, 17:50, 17:55, 18:02, 18:04 — triggers on PR 3235, no response
• 18:00 — @codex on bedrock-v/Vedrock PR 158 → review posted 18:05 (works)
• 18:08 — connector installation on PowerNukkitX org created (id 163061052), i.e. the previous installation had been removed
• 18:10, 18:21 — triggers on PR 3192, no response
• 18:51 — clean trigger on PR 3192, no response after 6+ minutes

What was verified

GitHub side is healthy:

• App installed org-wide, repository_selection: all, suspended_at: null
• Subscribed events include issue_comment, pull_request, pull_request_review, pull_request_review_comment
• Permissions: contents: write, issues: write, pull_requests: write, actions: write, checks: read, metadata: read, statuses: read, workflows: write
• The trigger comment posts fine and GitHub emits the mentioned event for codex
• PR head SHA resolves from the base repo (a230ccc84ac5b36a35529300b4a6d3357ba6d533)

Codex side:

• No task is created for these triggers. The failure is before task creation, not during execution.
• The repo stays listed under Settings → Code review even after the GitHub App is uninstalled from the org, which suggests a stale server-side record that the user cannot clear.
• Deleting the environment and reinstalling the App did not restore it.

Ruled out

• Not account, plan or quota: bedrock-v/Vedrock reviewed a PR at 18:05 on the same account, minutes before a failing trigger.
• Not fork PRs: PRs 3199, 3206 and 3207 were all from a fork of the same repo and were reviewed successfully during the working period.
• Not draft PRs: PR 3218 is a draft and was reviewed on 09-15.
• Not the repo preference rows: both the working and the broken repo are set to "Follow personal setting" for all three columns.
• Not trigger syntax: exact @codex review was used, identical to the working cases.

Expected

@codex review creates a review task for the repo, as it did until 09-15.

Actual

The trigger is silently discarded. Nothing is posted on the PR and no task is created.

Environment

• Repo: PowerNukkitX/PowerNukkitX (public, org-owned), base branch beta
• Working comparison repo: bedrock-v/Vedrock (public, org-owned), connector installation untouched since 09-13
• Example failing PR: https://github.com/PowerNukkitX/PowerNukkitX/pull/3192
• Connector installation id (PowerNukkitX): 163061052, created 2026-09-19 18:08 UTC

Possibly related

• #40115 — @codex review pinned to one workspace when a repo is connected to two workspaces
• #30858 — reviews stop after a repo ownership change, 👀 only, no review posted

No source file or test is named. Start by tracing the GitHub App connector installation record and the path handling the mentioned event after an installation is recreated; reproduce with @codex review on PowerNukkitX/PowerNukkitX and compare the working bedrock-v/Vedrock case. Done means a new trigger creates a Codex review task and posts the review.