codex - 💡(How to fix) Fix Codex mobile remote does not persist or re-list projectless conversations after reconnect

Summary

Codex mobile remote can connect to the Mac host and create new conversations, but projectless / no-working-directory conversations created after the first mobile connection do not show up again after disconnecting and reconnecting.

Observed behavior

• On the first mobile remote connection, the mobile UI shows all existing projectless / no-working-directory Codex conversations.
• After that first connection, newly created projectless conversations can be used normally while the current remote session is active.
• However, after leaving or disconnecting and then connecting again, those newer projectless conversations are gone from the mobile remote conversation list.
• A new conversation can still be created and interacted with, but that conversation also disappears on the next reconnect.

Expected behavior

Projectless / no-working-directory conversations created through mobile remote should remain discoverable and loadable after the mobile client disconnects and reconnects, as long as they still exist on the Mac host.

Why this looks specific

This does not look like a general relay, auth, or network failure:

• The mobile client can connect to the Mac host.
• New remote conversations can be created.
• Live interaction inside the new conversation works.
• The failure appears when the mobile client reconnects and tries to list or restore those projectless conversations.

This looks like an indexing, persistence, or conversation-discovery bug for projectless Codex threads in the mobile remote flow.

Environment

• Host: macOS Codex app
• Client: ChatGPT mobile Codex remote control
• Conversation type: projectless / no working directory
• Date observed: 2026-05-15