[Bug]: Codex chats moved from No project may be skipped by session import #32873

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

1. In Codex Desktop on macOS, start a local chat with No project using the default scratch folder. Send a short message.
2. Move that chat into an existing local project outside the scratch folder. As a control, start another chat directly in the same project and send a message.
3. On the same Mac, run T3 Code’s welcome wizard, select that project for import, and check whether both chats appear.

Expected behavior

If both recent chats are assigned to the selected project in Codex, the import should include both.

Actual behavior

I asked Codex about this workflow before trying it. Codex reviewed T3’s importer and flagged the possible failure below. The desktop steps above have not been run end to end.

T3’s scanner takes the first working directory it finds in a transcript, then excludes directories under ~/Documents/Codex. If moving the chat in Codex leaves that first recorded directory pointing to its original scratch folder, T3 will skip it even though Codex now lists it under the selected project. The control chat should still be eligible. First working directory · Excluded directories

Impact

Minor bug or occasional failure. This can leave a gap when migrating chats that started outside a project.

Version or commit

T3 Code v0.1.7 source inspected.

Environment

macOS, local Codex Desktop and local T3 Code.

Related

Discussion #27585 covers the general scratch-folder exclusion. This report is about importing a chat after it has been assigned to a project in Codex.