Android Remote direct entry stays on settings screen and does not show desktop projects

What happened

I paired the ChatGPT Android app with Codex Desktop on Windows using the QR code. The desktop is shown as ready/connected, but the Remote entry point behaves differently:

• Tapping the persistent “Remote connected” notification opens the actual remote control UI.
• Opening Remote directly from the Android app/sidebar only shows the Remote settings/setup screen.
• The Android app does not show the desktop’s local projects; it only shows the shared Chat area.
• To access remote projects, I have to tap the notification every time, even though the pairing remains present.

Expected behavior

After pairing once, opening Remote directly from the Android app should open the same connected desktop and show its projects without scanning a QR code again.

Steps to reproduce

1. Pair the Android app and Windows Codex Desktop by QR code.
2. Enable the remote connection on the desktop and leave it connected.
3. On Android, open the app sidebar and tap Remote.
4. Observe that the Remote settings/setup page is shown instead of the connected desktop and its projects.
5. Tap the “Remote connected” notification; this opens the correct remote control screen.

Environment

• Codex Desktop on Windows
• ChatGPT Android app
• Remote pairing completed successfully via QR code
• Clash/Mihomo proxy is used because the network does not support WebSocket reliably. Codex repeatedly retries the WebSocket connection and later falls back to HTTP.
• The desktop and Android account are paired; the notification deep link works.

Evidence collected

• The desktop-side enrollment state remains enabled after pairing.
• Local app-server logs show the Android Remote client successfully connecting and requesting config/read, model/list, thread/list, threadSection/list, and thread/resume.
• The desktop has project metadata for ego4d_pipeline, but the affected task’s persisted thread record had an empty project binding while separate desktop assignment metadata still mapped that task to the project.
• Repairing that single local binding did not change the Android app’s direct Remote entry behavior.
• No account IDs, access tokens, or private logs are attached.

Additional context

The desktop can see the phone authorization, and the Android app can see the desktop as ready. The failure is specifically the direct in-app Remote entry point and project list, not the QR pairing itself.

Start at the Android sidebar's Remote entry point and compare it with the working “Remote connected” notification deep link. Use the desktop enrollment state and local app-server logs for config/read, model/list, thread/list, threadSection/list, and thread/resume to trace the connected session and project metadata. Done means direct Remote opens the connected desktop and shows its local projects without another QR scan.