[Windows] Conversations remain unusable and cannot be archived after being moved out of a local project

Summary

Two Codex Desktop conversations remain unusable after being moved out of a local project. The project itself works normally again: project conversations can be opened and archived after these two conversations are removed from it. However, the two affected conversations still cannot be continued or archived.

This suggests the conversations retain stale or inconsistent project/thread metadata after being moved out of the project.

Product / area

• Product: Codex Desktop app
• Platform: Windows
• Area: local project conversation management, thread resume, archive, and project reassignment
• Project type: local Git project
• Sensitive data: no private project files or conversation contents are attached

Affected conversations

• hi我在接受朋友的邀请
• hi

Steps to reproduce

1. Open a local Git project in Codex Desktop.
2. Create or use the two conversations listed above.
3. Observe that the project conversation list and archive behavior become abnormal while these conversations are in the project.
4. Move both conversations out of the project.
5. Observe that the project's other conversations and archive behavior return to normal.
6. Try to open either affected conversation and send a new message.
7. Try to archive either affected conversation.

Actual behavior

• The project works normally after the two conversations are moved out.
• The two moved conversations remain broken:
  • cannot be continued normally;
  • cannot be archived;
  • they appear as stale/ghost conversation entries.
• The failure follows the conversations rather than the project.

Expected behavior

Moving a conversation out of a project should update its project association and leave it fully usable. The conversation should remain resumable, archivable, and removable from the sidebar.

Evidence

The conversations were verified as existing Codex threads, but their UI state remains unusable after reassignment. A screenshot showing the two affected entries is available if maintainers need it; it is not attached because it may contain account or local UI information.

Please investigate stale project/thread association or local conversation-index state after moving a thread out of a project. A repair/reindex path would also be helpful if the UI cannot recover the affected entries.

Workaround

Removing the two conversations from the project restores normal project conversation and archive behavior, but does not repair the affected conversations themselves.

Reproduce the project reassignment steps in Codex Desktop on Windows, focusing on the two affected conversations and their local conversation state. Done means moving conversations out of a local project leaves them resumable, archivable, and removable while the project's other conversations continue working normally.