Android Remote cannot open Windows-created Codex tasks; Android-created tasks work
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the listed failing and working task IDs, comparing how Windows-created and Android-created tasks are loaded in Android Remote. Done means every task shown in the Remote task list opens and synchronizes, including Windows-created tasks and forks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, rust
- Domain
- desktop-dev, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100