[Codex Cloud GitHub Review] `Codex Review Summary` progress comments create notification and automation noise

What issue are you seeing?

Product: Web / Codex Cloud GitHub Code Review — managed GitHub integration, not Codex CLI or codex-action.

Manually triggering a review with @codex review now creates a top-level PR comment titled Codex Review Summary while the review is still running. The comment contains review status such as Running and is later updated as the review progresses/completes.

Previously, the GitHub review flow was much less noisy for this use case:

1. @codex review
2. Codex reacts with 👀 to acknowledge the request
3. Codex performs the review
4. Codex posts the actual review/findings when finished, or indicates that no findings were found

The new progress comment is problematic because GitHub treats its creation as an ordinary PR conversation comment. That triggers notification and automation systems even though there is no actionable review result yet.

In my workflow, PR-comment notifications are forwarded to Slack. I now receive a notification when Codex starts reviewing, while the useful event is when the review finishes. Because the existing Codex Review Summary comment is subsequently edited rather than a new completion comment necessarily being created, notification systems can notify on the non-actionable start event but not on completion.

This also creates automation noise beyond notifications. A public example is Generous-Corp/pulp#529, where a post-merge sweep currently collects multiple Codex Review Summary comments as unresolved bot comments:

https://github.com/Generous-Corp/pulp/issues/529

I could not find a Code Review setting that disables these progress comments while keeping managed Codex review enabled.

What steps can reproduce the bug?

1. Enable the managed Codex Cloud GitHub Code Review integration for a repository.
2. Open a pull request.
3. Add a comment containing @codex review.
4. Codex reacts with 👀 as expected.
5. Observe that chatgpt-codex-connector also creates a top-level Codex Review Summary PR comment while the review is still running.
6. Observe that GitHub comment notifications / comment-based automations can trigger on this non-actionable progress comment.
7. When the review progresses or completes, observe that the existing summary comment can be updated rather than completion necessarily producing an equivalent new comment event.

Observed with the managed Cloud review integration on 2026-09-02.

What is the expected behavior?

Starting a review should not create a top-level PR conversation comment solely to communicate ephemeral progress.

The previous minimal-comment behavior is preferable:

• use 👀 to acknowledge that the review has started;
• publish GitHub review findings/comments when the review has completed;
• if there are no findings, a final completion indication is fine.

If richer progress visibility is needed, it should use a GitHub-native status mechanism such as a Check Run rather than a PR conversation comment.

Related issue #27691 already requests GitHub Check Runs for Codex Cloud review status (queued, running, completed, failed):

https://github.com/openai/codex/issues/27691

That would provide progress visibility without polluting the PR conversation or triggering comment-based notification/automation systems.

At minimum, please provide a setting to disable Codex Review Summary progress comments and retain the previous minimal-comment behavior.

Additional information

This is specifically about the first-party managed Codex Cloud GitHub Code Review product, not Codex CLI, Codex Desktop local review, or the open-source GitHub Action.

The core issue is not that review progress is visible. The issue is using a top-level PR conversation comment as an ephemeral progress/status channel. PR comments have notification and automation semantics that make them a poor fit for transient review state.

Related:

• #27691 — GitHub Integration: Surface Codex Cloud PR Reviews as GitHub Check Runs
• Generous-Corp/pulp#529 — public real-world example of Codex Review Summary comments being picked up as unresolved bot-comment noise

No repository files or tests are identified; first determine whether the managed Codex Cloud GitHub integration is implemented in this repository or handled elsewhere. Read related issue #27691 and define completion as avoiding non-actionable top-level progress comments, or providing the requested setting or Check Run behavior.