Desktop Cloud Projects, ChatGPT Projects, Codex, and Sites appear to use inconsistent project identities

Environment

  • Surface: Web + Linux desktop app
  • Browser or app version: Chrome
  • Affected feature and model, if relevant: ChatGPT Projects / Codex Projects / Cloud Projects / Sites integration. Model not relevant.

Bug

A project created in the desktop app using the Cloud project type appears under both ChatGPT → Projects and Codex → Projects in the desktop app, but the same project does not appear on chatgpt.com.

A second project created directly on chatgpt.com behaves differently. After restarting the desktop app, both projects appear there, suggesting they are different underlying project types even though both are presented to the user as Projects.

There also appears to be asymmetric migration behavior: conversations from the original desktop-created project can be moved into the web-created ChatGPT Project, but conversations cannot be moved in the opposite direction.

The original project contains development history and is associated with a deployed Site, so it is unclear whether moving its conversations/files could affect Codex context, Site source, or deployment relationships.

Expected behavior: a Cloud Project should have one stable identity across ChatGPT web, desktop, Codex, and Sites, or the UI/documentation should clearly identify different project types and provide a supported migration/conversion path.

Reproduction

  1. Open the ChatGPT desktop app.
  2. Create a new Project.
  3. Select Cloud as the project type.
  4. Add conversations and perform development work in the project.
  5. Confirm that the project appears under ChatGPT → Projects in the desktop app.
  6. Switch to Codex in the desktop app and confirm that the same project also appears there.
  7. Open chatgpt.com using the same account/workspace.
  8. Check the Projects list and search for the project.
  9. Observe that the desktop-created Cloud Project is not available.
  10. Create a new Project directly on chatgpt.com.
  11. Restart the desktop app.
  12. Observe that both the original desktop-created project and the new web-created project now appear in the desktop app.
  13. Attempt to move conversations between the two.
  14. Observe that movement appears possible from the original project to the web-created project, but not in the opposite direction.

This suggests that two different underlying project types are being exposed under the same Projects UI.

Diagnostics

Exact error or screenshot: No explicit error message is displayed.

Observed UI behavior:

  • Desktop-created Cloud Project is visible under ChatGPT Projects on desktop.
  • The same project is visible under Codex Projects on desktop.
  • The project is absent from chatgpt.com.
  • The project is also absent from the relevant web Codex project/environment selector.
  • A web-created ChatGPT Project appears normally on both web and desktop after restarting the desktop app.
  • Conversation migration behavior between the two project types is asymmetric.

When it happened (with timezone) and how often: The behavior is reproducible consistently.