Auto-review blocks publishing an existing Sites project

What version of the Codex App are you using (From “About Codex” dialog)?

26.825.6671.0

What subscription do you have?

free

What platform is your computer?

windows 11 home

What issue are you seeing?

I am using the ChatGPT desktop app on Windows to build and publish an existing private Sites project.

Publishing previously worked, but Auto-review now blocks the source upload to the project’s existing repository on git.chatgpt-team.site. The repository URL and short-lived credential were provided by the Sites tooling for this exact project.

The pending code change is harmless: it only removes a persistent informational footer. The project builds and tests successfully, contains no new API keys or portfolio data, and the existing Site remains owner-only.

I explicitly approved publishing, but Auto-review still classified the destination as unverified. The /approve command does not display a denial picker in my desktop app.

Expected result:
Publishing an update to the existing Sites-owned repository should be allowed, or the app should provide a working narrow approval flow.

Actual result:
The upload is denied before execution, so the new Site version cannot be saved or deployed.

Feedback ID:
01a043c5-c08e-7b23-8e12-f38fe6da74d9

Environment:

ChatGPT desktop app

Windows

Sites project

Permission mode: Approve for me

What steps can reproduce the bug?

1. Open an existing private Sites project in the ChatGPT desktop app on Windows.
2. Make a harmless source change. In my case, the change only removed a persistent informational footer.
3. Build and validate the project successfully.
4. Ask Codex to publish the updated Site.
5. Sites provides a short-lived, repository-scoped credential and the existing project repository on git.chatgpt-team.site.
6. Codex attempts to push the validated source to that repository.
7. Auto-review denies the action before it runs, stating that the private project source would be sent to an unverified external repository using a credential.
8. Explicitly authorize this exact publication in the conversation and retry. Auto-review still denies it.
9. Enter /approve in the desktop app. No denial picker or approval menu appears.

No code snippet is required to reproduce this; the failure occurs during the standard Sites publishing workflow.

Expected:
Codex should recognize the Sites-provided repository as belonging to the existing project, or show a working narrow approval prompt.

Actual:
The source upload is blocked, so the new Site version cannot be saved or deployed.

Feedback/session ID:
01a043c5-c08e-7b23-8e12-f38fe6da74d9

What is the expected behavior?

No response

Additional information

No response

Start by reproducing the standard Sites publishing workflow in the ChatGPT desktop app on Windows, then inspect the Auto-review denial and the /approve behavior for the Sites-provided repository and credential. Done means an existing Sites-owned repository is recognized as verified, or a working narrow approval flow permits the upload.