Android Remote cannot open Windows-created Codex tasks; Android-created tasks work

Open 💬 4 comments Opened Aug 21, 2026 by kevin-kore

💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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

26.818.31338

What subscription do you have?

Business Plan

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

ChatGPT Remote on my Android tablet successfully connects to the Codex Windows app and displays the task list. However, opening any task created on Windows produces an indefinite loading spinner.

A task created from the Android tablet on the same Windows host and in the same worktree opens normally. Messages entered on Windows appear on the tablet and vice versa. This confirms that pairing, connectivity, the account, and message synchronization are working.

Environment:

Host: Codex/ChatGPT Windows app
Windows app version: 26.818.3698.0
Android tablet: [model]
Android version: [version]
ChatGPT Android app version: [version]
Google Play reports that no update is available

Steps to reproduce:

Pair the Android tablet with the Windows Codex app.
Create or open a task on Windows.
Open Remote on Android and select that task.
The task displays a loading spinner indefinitely.
Create a new task from Android on the same host and worktree.
That Android-created task opens and synchronizes normally.

Expected result:

Any existing task shown in the Remote task list should open, regardless of whether it was created on Windows or Android.

Actual result:

Only the task created from Android opens. Windows-created tasks—including newly created tasks and a newly created fork—spin indefinitely.

Troubleshooting already completed:

Force-stopped the Android app
Cleared the Android app cache
Cleared all Android app storage/data
Signed out and back in
Removed and re-established the pairing
Fully restarted the Windows app
Confirmed that both apps are current
Opened the affected task on Windows before attempting it on Android
Created a fresh fork of an affected task
Confirmed that Windows can open, read, and continue all affected tasks

The problem persists after all of these steps.

Example task IDs:

Failing current task: 01a02218-e0a3-7271-bbbf-8a29f081159f
Failing older task: 01a02178-a9d5-7ff1-9e5c-c68b50de866a
Failing fresh fork: 01a0222c-dcbc-7560-a28d-4e8eb01484c6
Working Android-created task: 01a02227-1a62-7b81-a3a7-bd4f6137373a

This appears to be an Android Remote task-loading defect specific to tasks originating on the Windows host.

What steps can reproduce the bug?

Feedback ID: 01a02218-e0a3-7271-bbbf-8a29f081159f

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 7 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

#39815

Powered by Codex Action

hyeonsangjeon · 7 days ago

Confirmed a closely related Android -> macOS variant. I cannot yet confirm that task origin is the differentiating factor described in the original report, so I am not claiming the same root cause, but the half-connected behavior is the same.

Environment

Affected client: ChatGPT Android (exact affected device and app build not yet independently captured)
Host: macOS 26.5.2 (25F84)
Active ChatGPT/Codex Desktop: 26.818.22352 (bundle build 6872)

Observed behavior

Start Codex Desktop on the Mac with Remote enabled.
In ChatGPT Android, select the Mac host, project, and an existing task.
The host/project/task lists load, the task header reports that it is connected, and the composer is bound to the selected Mac host.
The conversation body remains on gray skeleton placeholders indefinitely.
Send a text prompt from Android anyway.
The prompt reaches the Mac and executes there, but Android still does not hydrate either the existing history or the new response.

The desktop can open and render the same tasks normally. This reproduced on two recent tasks (roughly 20-50 minutes old), so it is not limited to old/inactive history.

Troubleshooting already tried:

force-stopped and restarted ChatGPT Android;
fully restarted Codex Desktop;
rebooted one Mac host;
tested with Tailscale disconnected;
retried multiple recent tasks.

The important split is:

Android -> Mac command/write path: working
Mac -> Android history/response hydration/rendering: not working

Expected: once task metadata loads and the send path is functional, Android should hydrate the existing message history and render new responses.

Possibly related: #36491, #37173, #37598, and the iOS/macOS hydration variant #22705.

_Corrections (2026-08-21 KST): I initially included SM-F721N / Android 16 from a different phone connected over ADB; those details were removed. I also corrected the host version to the active unified ChatGPT/Codex app (26.818.22352); 26.803.41515 was from an older inactive Codex.app still installed alongside it._

hyeonsangjeon · 6 days ago

Additional cross-device control (2026-08-21 KST)

I reproduced the existing-task hydration failure on a freshly connected second Android device:

Device: SM-F721N
OS: Android 16 (SDK 36)
ChatGPT Android: 1.2026.223
Setup: fresh sign-in / newly connected to the same macOS Remote host

The Remote task header shows the host with a green connected indicator, but opening an existing task still leaves the conversation body on gray skeleton placeholders indefinitely. The same task remains usable on Desktop.

This cross-device result rules out the original phone's local cache, device-specific pairing keys, and a stale enrollment on only that phone. The failure follows the Android Remote existing-task hydration path.

A local screenshot was captured for verification but is not being uploaded publicly because it is not necessary to establish the reproduction.

arthurlapertosa · 6 days ago

Same here. Short threads work, but not long threads. I also connect my android phone to Linux hosts, and it also cannot load long threads from them.