What version of the Codex App are you using (From “About Codex” dialog)?
OpenAI.Codex 26.721.4979.0 OpenAI.Codex_26.721.4979.0_x64__2p2nqsd0c76g0
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
A conversation created in the ChatGPT desktop app appears in the conversation list on chatgpt.com, but it cannot be moved to a Project until the conversation has first been opened and fully loaded in the web interface.
Before opening the conversation on the web, attempting to use Move to project from the conversation's sidebar menu either fails, does nothing, or does not complete the move.
After I open the same conversation on chatgpt.com and wait for its contents to load, the Move to project action works normally.
This creates an unnecessary dependency on opening every desktop-created conversation in the browser before it can be organized into a Project.
What steps can reproduce the bug?
- Open the ChatGPT desktop app.
- Create a new Chat conversation and send at least one message.
- Open chatgpt.com in a browser using the same account.
- Confirm that the newly created conversation appears in the web sidebar.
- Do not open the conversation.
- Open the conversation's sidebar context menu and select Move to project.
- Observe that the conversation is not moved successfully.
- Open the conversation and wait for its messages to load.
- Return to the context menu and select Move to project again.
- Observe that the conversation can now be moved successfully.
What is the expected behavior?
A synchronized conversation should be movable to a Project directly from the web sidebar, regardless of whether that conversation has previously been opened or loaded in the current browser session.
Project assignment should operate on the persisted conversation metadata and should not depend on the web client first loading the full conversation.
Additional information
The conversation itself is synchronized correctly and is visible in the web sidebar. The issue appears to affect the Project move operation before the conversation has been hydrated or loaded by the web client.
I can reproduce the issue with conversations originally created in the desktop app.
A potentially related issue is #35826, which reports that the Windows desktop app does not expose the Move to project action. However, this report concerns a different web-side behavior: the action is available on the web, but it does not work until the conversation has first been opened and loaded.
What version of the Codex App are you using (From “About Codex” dialog)?
OpenAI.Codex 26.721.4979.0 OpenAI.Codex_26.721.4979.0_x64__2p2nqsd0c76g0
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Windows Microsoft Windows NT 10.0.26200.0 x64
What issue are you seeing?
A conversation created in the ChatGPT desktop app appears in the conversation list on chatgpt.com, but it cannot be moved to a Project until the conversation has first been opened and fully loaded in the web interface.
Before opening the conversation on the web, attempting to use Move to project from the conversation's sidebar menu either fails, does nothing, or does not complete the move.
After I open the same conversation on chatgpt.com and wait for its contents to load, the Move to project action works normally.
This creates an unnecessary dependency on opening every desktop-created conversation in the browser before it can be organized into a Project.
What steps can reproduce the bug?
What is the expected behavior?
A synchronized conversation should be movable to a Project directly from the web sidebar, regardless of whether that conversation has previously been opened or loaded in the current browser session.
Project assignment should operate on the persisted conversation metadata and should not depend on the web client first loading the full conversation.
Additional information
The conversation itself is synchronized correctly and is visible in the web sidebar. The issue appears to affect the Project move operation before the conversation has been hydrated or loaded by the web client.
I can reproduce the issue with conversations originally created in the desktop app.
A potentially related issue is #35826, which reports that the Windows desktop app does not expose the Move to project action. However, this report concerns a different web-side behavior: the action is available on the web, but it does not work until the conversation has first been opened and loaded.