Windows host pairs with Android Remote, but conversations fail to load; `/wham/tasks/list` returns 503

Summary

Codex Remote on Android can successfully pair with a Windows host and the phone appears as an authorized/recently connected device in the desktop app, but the mobile Remote view can no longer access the Codex conversations/tasks from that host.

This worked previously and then stopped suddenly. Local diagnostics on the Windows host did not find a process, network, TLS, DNS, proxy, VPN, firewall, Defender, AppX, or Workspace dependency failure. The strongest signal in the desktop logs is a backend 503 on /wham/tasks/list, which lines up directly with the point where Remote needs to retrieve the host's Codex tasks/conversations.

Environment

• Host: Windows, ChatGPT/Codex desktop app
• Desktop package version: 26.818.2872.0
• Client: ChatGPT Android app (beta channel at the time the issue was observed; exact mobile build not recorded)
• Remote pairing: succeeds
• Control this PC / Remote connections: enabled
• Android device appears in the desktop connected-device list and shows a recent connection
• Codex Workspace dependency diagnostic: reports healthy

What is happening

The Android device can be paired to the Windows host, but after pairing the Remote surface cannot access/load the Codex conversations from the PC.

The pairing itself appears healthy. The failure seems to occur later, during retrieval/hydration of the task/conversation list.

Relevant desktop log evidence

After a Windows restart, the following backend responses were observed in the local ChatGPT/Codex logs:

2026-08-20 23:41:07  503  /wham/tasks/list
2026-08-20 23:50:03  503  /wham/usage
2026-08-21 00:42:17  401  /accounts/

Additional history on 2026-08-20 included:

15 x 503 on /sentinel/heartbeat
4 x 500 on /sentinel/heartbeat

No credentials, cookies, tokens, account IDs, device IDs, or conversation content are included here.

Local diagnostics already performed

• Desktop app restarted
• Windows fully restarted
• Android device revoked and re-paired
• Remote connections disabled/re-enabled
• Android app reinstalled
• Windows ChatGPT app updated
• Codex Workspace diagnostic run: dependencies reported healthy
• Desktop AppX package state: Ok
• Desktop processes checked: running and responsive
• 298 local Remote IPC responses (status, enable, pairing, device list/revoke) inspected: 0 local IPC errors
• DNS: working
• HTTPS: working
• TLS 1.3 / certificates: valid
• System clock: within ~0.4 s of server time
• WebSocket upgrade path: not generally blocked (application-level response is received)
• User proxy: disabled
• WinHTTP: direct access
• Active VPN: none detected
• No relevant Windows crash/hang, Crashpad, Code Integrity, AppLocker, or Defender block found

Suspected failure stage

The observed flow appears to be:

1. Host discovery / pairing: works
2. Authentication / device registration: works sufficiently for the phone to appear as connected
3. Remote channel establishment: no local failure found
4. Network/WebSocket transport: no local blanket block found
5. Task/conversation retrieval: fails

The 503 /wham/tasks/list is the most direct evidence for stage 5.

Expected behavior

After pairing an Android device with an online Windows ChatGPT/Codex host, the Remote view should list and allow access to the Codex conversations/tasks available on that host.

Actual behavior

The Android device pairs successfully and is visible as an authorized/recently connected device on Windows, but the Remote client cannot access the Codex conversations/tasks.

Additional context

There are other reports of Windows + Android Remote state/listing problems, but I did not find an existing issue that includes the same 503 /wham/tasks/list evidence.

Because local networking and the Remote IPC layer look healthy, this may be a transient service-side failure or an account/workspace-side Remote state problem.

If maintainers need additional diagnostics, I can provide sanitized timestamps/log excerpts without exposing account or authentication data.

Begin with the Android-to-Windows Remote flow and the desktop log entries for /wham/tasks/list, /wham/usage, and /sentinel/heartbeat. Reproduce the conversation-list request if possible, then determine whether the 503 occurs in the client path or the service; done means Remote can retrieve and display the host's tasks, with sanitized logs documenting the result.