One-click migration omitted an existing project from Codex Desktop Hub and therefore from Android Remote
Correction / root cause
The original report assumed that ChatGPT Android Remote was omitting a project that already existed in the connected Windows Codex Desktop Hub.
After regaining access to the computer, I found that this specific project had not been added to the Codex Desktop Hub at all during the one-click migration/integration flow. Because the project was absent from the Hub, it was also absent from Android Remote and from the new-session project selector.
After I manually added the project to the Codex Desktop Hub and created a Codex session in it, the project appeared in Android Remote immediately.
So this specific reproduction is a migration/import omission, not a confirmed Remote indexing failure.
Environment
- Host: Windows 11 Pro
- Mobile client: ChatGPT for Android
1.2026.188 - Android: 16
- Subscription: ChatGPT Pro
- Flow: one-click migration/integration into Codex Desktop Hub, then ChatGPT Android → Codex Remote → connected Windows host
Steps to reproduce
The exact selection rule used by the migration is not yet known, but the observed flow was:
- Use the one-click migration/integration flow to bring existing projects into the Codex Desktop Hub.
- Observe that most projects are added, but at least one existing project is omitted from the Hub.
- Connect to the Windows host from ChatGPT Android using Codex Remote.
- Observe that the omitted project is also missing from the Remote project list and from the new-session selector.
- On the computer, manually add the missing project to the Codex Desktop Hub.
- Create a Codex session in that project.
- Return to Android Remote.
- Observe that the project now appears.
Expected behavior
The migration should either:
- import every eligible existing project into the Codex Desktop Hub, or
- clearly report which projects were skipped and why.
A silently omitted project is difficult to distinguish from a Remote synchronization/indexing bug.
Actual behavior
The migration silently omitted at least one project. Because Android Remote only exposed projects known to the Codex Desktop Hub, the project was unavailable remotely until it was manually added on the computer.
Additional note
I have separately seen intermittent cases where projects that were believed to exist in the Hub did not appear in Remote, so the broader Remote listing issues reported in #23098, #24749, and #31370 may still be real. However, this particular project was missing because migration had not registered it in the Hub, and this issue is now scoped to that reproducible migration behavior.