[Android Remote][Windows] QR pairing succeeds, then tasks stop loading and the client disconnects when outbound queue fills

What version of the Codex App are you using (From “About Codex” dialog)?

Codex App for Windows 26.818.2872.0; ChatGPT for Android 1.2026.223 (20)

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64 (Windows 11 Home); mobile: Samsung Galaxy Z Fold8

What issue are you seeing?

ChatGPT for Android Remote Control pairs successfully with Codex App for Windows: scanning the QR code registers the Galaxy device and the device name appears on the Windows host. However, Android then shows a red exclamation mark and the Korean error ChatGPT 데스크톱에 연결하지 못했습니다 ("Couldn't connect to ChatGPT desktop").

When a connection succeeds temporarily, the task list can appear briefly. Opening either an existing task or a newly created minimal task then remains loading or the mobile Remote connection is lost. Force-stopping and reopening the Android app can restore the connection temporarily, but the problem returns.

The Windows host remains enrolled with Remote Control enabled. In a reproduced disconnect, the host control WebSocket remained connected and the app-server had already processed Remote requests such as initialize, thread/list, thread/resume, and thread/turns/list. The per-device connection was then closed with the following sanitized sequence:

disconnecting slow connection after outbound queue filled
forwarding remote control connection closed transport event

No concurrent 401, 403, 409, authentication, TLS, host-WebSocket, database-lock, app crash, or resource-exhaustion error was observed.

What steps can reproduce the bug?

1. On Windows, open Codex App and enable Remote Control.
2. Choose Add device and scan the QR code with ChatGPT for Android 1.2026.223 (20).
3. Confirm that the Galaxy device appears in the Windows host's connection list.
4. Open Remote on Android.
5. Observe that the task list either appears briefly or remains loading.
6. Open an existing task or a newly created minimal/empty task.
7. Observe the red exclamation mark and ChatGPT 데스크톱에 연결하지 못했습니다, or an indefinitely loading task.
8. Force-stop and reopen the Android app. The connection may work temporarily, then fails again.

The issue still reproduces after:

• Fully quitting and restarting the Windows app
• Updating the Windows app
• Reinstalling ChatGPT for Android
• Revoking/removing and recreating the QR pairing
• Creating a new minimal task specifically for mobile display testing

What is the expected behavior?

After successful QR enrollment, the Android client should maintain a stable Remote session, list and render host tasks, and continue receiving task history and live turn updates without requiring repeated force-stops.

Additional information

• First reproduced and diagnosed: 2026-08-21 (Asia/Seoul)
• Mobile: Samsung Galaxy Z Fold8
• ChatGPT for Android: 1.2026.223 (20)
• Windows host package: 26.818.2872.0
• Related issue: #37526 (the earlier queue-full fix appears to have missed the ChatGPT relay/Remote path)
• Similar user-facing environment: #22733

Task-size check:

• Existing large task: approximately 319 MB
• New task: approximately 0.87 MB
• Ultra-light display-test task: approximately 0.11 MB

The issue therefore does not appear limited to one large task history.

Diagnostic caveat: detailed local log inspection can itself generate app-server output events and may affect the exact queue timing. However, the user-visible disconnects began before detailed inspection and also reproduced with the ultra-light display-test task.

Account IDs, installation/environment/enrollment IDs, task IDs, tokens, local paths, usernames, hostnames, and business data have been intentionally omitted.

No source files or tests are named. Start by reproducing the Android Remote pairing flow and tracing the per-device connection around the reported “outbound queue filled” and slow-connection messages, including the initialize, thread/list, thread/resume, and thread/turns/list requests. Done means the paired client keeps its session, loads tasks, and receives history and live updates without disconnecting.