Android Codex Remote disconnects before thread/resume responses reach client on Windows host

Codex Remote on Android 16 cannot reliably maintain a session with my Windows ChatGPT/Codex host.

Feedback ID:
01a01fa0-40fd-7532-a1a5-7e12d30a87e8

Environment:

• Windows package: OpenAI.Codex_26.818.3698.0
• App-server build: 26.818.31338
• Android 16
• Samsung SM-S938B
• Android client: codex_chatgpt_android_remote

Symptoms:

• QR pairing succeeds.
• Android can discover the Windows host, projects and recent threads.
• Opening Codex threads often remains indefinitely on grey loading placeholders.
• Remote cycles through Connecting, Looking for ChatGPT desktop, Reconnecting, and Failed to connect to ChatGPT desktop.
• Reproduces across multiple threads and both Wi-Fi and 5G.

Local diagnostics:

• Android reaches the host and sends thread/resume requests.
• All 35 local transcript files exist.
• Thread-state and log databases pass integrity checks.
• 46 Android Remote client connections closed within one hour.
• 27 host responses were dropped after the corresponding client connection had already disconnected.
• Host logged: "Dropping message for disconnected connection".
• Main Remote WebSocket also reset once without a closing handshake.
• No relevant Windows crashes, proxy, authentication errors, or missing-thread errors.

Troubleshooting already performed:

• Latest Windows and Android apps
• Phone reboot
• Force stop / cache clear
• Android sign-out/sign-in
• Wi-Fi and 5G testing
• Fresh revoke + QR pairing
• Windows desktop restart
• Full Windows ChatGPT uninstall/reinstall
• Multiple Codex threads tested

Likely failure sequence:

1. Android opens a Remote connection and sends thread/resume.
2. That connection disconnects or is replaced.
3. Windows completes the request against the old connection ID.
4. The host drops the response because the connection no longer exists.
5. Android remains on loading placeholders and starts reconnecting.

Failure window:
21 August 2026, approximately 12:46–12:51 UTC, continuing afterwards.

Please investigate Android Remote connection churn and stale connection-ID response routing/replay after reconnect, and correlate against the Feedback ID above.

Start by tracing the Android Remote WebSocket connection lifecycle and the Windows host's thread/resume request and response-routing paths described in the issue. Reproduce the reconnect sequence using the listed diagnostics and Feedback ID, then verify that responses are delivered or replayed after connection replacement instead of being dropped for stale connection IDs.