openai / openai/codex

[Bug] Android Remote became unusable: Windows host appears disconnected and long tasks do not open

Open
#39,947 17 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug connectivity remote windows-os
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)?

ChatGPT/Codex Desktop for Windows 26.814.5167.0; bundled codex-cli 0.148.0-alpha.15.

Android controller: latest ChatGPT build offered by Google Play on 2026-08-21; Google Play reports no update available. The exact Android build, OS version, and device model were not captured yet.

What subscription do you have?

Paid ChatGPT account (exact tier intentionally omitted).

What platform is your computer?

Host: Microsoft Windows NT 10.0.26200.0 x64

Controller: ChatGPT for Android.

What issue are you seeing?

Codex Remote from ChatGPT Android became effectively unusable over approximately the last 24 hours after working reliably about 48 hours ago.

There are two reproducible failure modes:

  1. In most attempts, Remote does not connect to the Windows host at all. The host is shown with a red/offline indicator even though ChatGPT/Codex Desktop is open, awake, online, and signed in. Android displays:

    Failed to connect to ChatGPT desktop

    Make sure the ChatGPT desktop app is open, then try again.

  2. When Remote does connect, it lists the tasks currently running on the Windows host. Short/small tasks open normally, but selecting a long task does not open the transcript and eventually shows the host/task as disconnected. This makes the tasks that most need remote supervision inaccessible.

The regression began around 2026-08-20. Other users known to the reporter independently describe the same recent Android Remote failure. The OpenAI status page showed no Remote Connections incident when checked on August 20 and 21.

What steps can reproduce the bug?
  1. Keep ChatGPT/Codex Desktop 26.814.5167.0 open on an online Windows host with Remote enabled.
  2. Open ChatGPT for Android, using the latest build available from Google Play.
  3. Enter Remote and select the paired Windows host.
  4. Frequently, observe the red/offline host indicator and the Failed to connect to ChatGPT desktop error despite the Desktop app being open.
  5. Retry until the connection succeeds and the host task list appears.
  6. Open a small/recent task; it normally loads.
  7. Open a long-running task with substantial history; it remains unavailable or transitions to disconnected instead of rendering the transcript.
What is the expected behavior?

Android Remote should reliably connect to an awake, online, paired Windows host. After connecting, every visible task should open at least a bounded recent transcript tail without requiring the complete history to hydrate first. Long tasks must not block or tear down the host connection.

Additional information

A screenshot captured around 2026-08-21T14:28Z shows the paired Windows host offline and the exact connection error above. The host name, account information, task names, IDs, and contents are omitted from this public report. A sanitized screenshot and diagnostics can be provided privately.

Related issue #38023 documents Android Remote failing to hydrate an idle large task and a turn/start timeout. The long-task symptom overlaps with that report. This issue is distinct because the primary regression frequently occurs before any task is selected: Android marks the Windows host disconnected and cannot enter Remote at all.

Related issue #37126 documented old Android chats not opening, but the reporter closed it after adopting shorter chats as a workaround rather than after a confirmed product fix.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. First reproduce the Android Remote connection failure and the long-task transcript failure using the listed Windows and Android versions, then collect the sanitized diagnostics mentioned in the report. Done means a paired online host connects reliably and long tasks open a bounded recent transcript without disconnecting the host.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, rust
Domain
mobile-dev, networking
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.