[Windows][Android Remote] Individual 2–5 MB tasks hang on loading skeletons while a 1 MB task opens

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

• Windows Codex desktop package: OpenAI.Codex 26.818.4152.0
• Bundled app-server observed locally: 0.149.0-alpha.4.1
• Android ChatGPT build: not captured; Google Play offered no newer update during troubleshooting

What subscription do you have?

Not disclosed. Pairing and Remote authentication succeed.

What platform is your computer?

Windows desktop host (MSI laptop) with ChatGPT/Codex Desktop. Remote client is the ChatGPT Android app.

What issue are you seeing?

Android Remote connects to the Windows host and loads the task list, but opening certain larger existing tasks leaves the message area on loading skeletons indefinitely. The client then disconnects/reconnects or returns to the Remote connection flow.

The Remote status dialog can show an active remote session and the correct thread identifier, while simultaneously showing:

• Folder: Unavailable
• Context: Unavailable

The local folder exists and is readable on the Windows host, and the same affected task can be opened/read locally.

A size-correlated control test was observed:

| Existing task | Local rollout size | Android Remote |
| --- | ---: | --- |
| Small control task | ~1.04 MB | Opens normally |
| Affected task A | ~2.07 MB | Loading skeleton indefinitely / reconnect |
| Affected task B | ~4.77 MB | Loading skeleton indefinitely / reconnect |

The failing ~2.07 MB task completed a local thread/read in approximately 47 ms, so local storage access and parsing were not slow. The failure occurs specifically during Remote/mobile hydration or rendering.

Other partial functionality still works:

• Remote task list can load.
• Push notifications from Codex arrive on Android.
• Image attachments sent from Android reach the desktop task.
• A smaller task can be opened and used.
• The Windows desktop process remains responsive.

This makes a general firewall, DNS, pairing, or host-offline failure unlikely. It appears to be a per-thread Remote hydration/envelope/rendering defect.

What steps can reproduce the bug?

1. Run Codex Desktop on Windows and enable Remote.
2. Pair/connect ChatGPT Android to the Windows host.
3. Open a smaller existing task whose local rollout is about 1 MB.
4. Observe that the task opens and renders normally.
5. Return to the Remote task list.
6. Open an existing task whose rollout is about 2–5 MB and contains several large JSONL records.
7. Observe loading skeletons indefinitely.
8. Open Remote status: the session may be active and show the correct thread, but Folder and Context are unavailable.
9. The mobile client may disconnect/reconnect and still cannot render the conversation.
10. Open/read the same task locally on Windows; it succeeds.

What is the expected behavior?

Any task shown in the Remote list should open. Larger histories should be paged or hydrated incrementally. If full history cannot be transferred, the newest turns and composer should remain usable with a clear partial-history warning.

What is the actual behavior?

The individual task remains on loading skeletons, Folder/Context are reported unavailable, and Remote may reconnect repeatedly. The conversation cannot be read or continued from Android even though the host and task are available locally.

Troubleshooting already completed

• Full Windows restart
• Android app reset/reinstallation
• Remote device revoked and paired again
• Remote disabled and re-enabled
• Desktop and mobile app update checks
• Tested another smaller task successfully on the same host/account
• Verified affected local project folders exist and are readable
• Verified an affected task reads locally in milliseconds
• No changes to firewall, DNS, routes, VPN/Tailscale, or server security were made because the per-task control test did not support a network-wide cause

Sanitized log signals

Desktop logs around the broader failure pattern contained repeated messages matching:

ResizeObserver loop completed with undelivered notifications
Received turn/started for unknown conversation

Raw logs and rollout files are not attached because they contain private project paths and conversation/code content. Sanitized excerpts or timestamps can be provided if maintainers identify a specific diagnostic window.

Related issues

• #36423 reports an oversized thread/read exceeding the Remote envelope on macOS, but only with a roughly 615 MiB rollout. This Windows/Android reproduction fails at approximately 2–5 MB.
• #37598 reports incomplete Android rendering of a CLI session.
• #39845 reports Android failing to open Windows-created tasks, but the present control shows that a smaller Windows task opens while larger Windows tasks fail.
• #39860 concerns oversized thread/list; here the list loads and the failure begins after selecting an individual task.

Privacy

No account identifiers, device identifiers, local usernames, private paths, authentication material, conversation text, server data, or raw session files are included. Screenshots showing the loading state and status dialog are available if a secure upload is requested.