openai / openai/codex

Windows Remote Control: Android pairing succeeds but desktop keeps zero remote connections

Open
#39,865 1 comment 2 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?
  • Windows AppX package: OpenAI.Codex 26.810.7004.0
  • About dialog showed: 26.810.52044
Subscription

ChatGPT Plus

Platform
  • Host: Windows 11 x64
  • Mobile: Android 17, Pixel 7a
Issue

Codex Remote Control pairing from Android succeeds, and the Windows host is visible on the phone, but the host remains unavailable and the phone cannot connect.

The Android device also appears in the desktop Remote/Connections settings after pairing. However, the desktop Remote Connection Manager repeatedly reports zero saved, managed, discovered, and auto-connect connections.

Reproduction
  1. Open Codex/ChatGPT desktop app on Windows 11.
  2. Enable Remote Control / device control.
  3. Pair an Android 17 Pixel 7a using the QR flow.
  4. Pairing reports success and the Windows host appears on Android.
  5. Attempt to connect to the Windows host from Android.
  6. Android reports that it cannot connect to the ChatGPT desktop app / host is unavailable.
Expected behavior

After successful pairing, the Android ChatGPT Remote view should connect to the online Windows Codex host.

Actual behavior

Pairing succeeds, but connection fails and the host is shown as unavailable.

Desktop log evidence

The desktop log repeats approximately every 15 seconds:

load_completed savedRemoteConnectionCount=0 totalConnectionCount=0
reconcile_completed creationFailureCount=0 nextConnectionCount=0 previousConnectionCount=0
refresh_completed autoConnectConnectionCount=0 codexManagedConnectionCount=0 discoveredConnectionCount=0 nextConnectionCount=0 previousConnectionCount=0
refresh_remote_control_started previousConnectionCount=0
reconcile_completed creationFailureCount=0 nextConnectionCount=0 previousConnectionCount=0
refresh_remote_control_completed autoConnectConnectionCount=0 nextConnectionCount=0 previousConnectionCount=0

This continues even immediately after attempting a connection from Android.

Diagnostics already performed
  • QR pairing revoked and performed again successfully
  • Desktop app completely restarted
  • Android app restarted
  • Windows app Repair performed: no change
  • Windows app Reset, followed by fresh login and fresh pairing: no change
  • DNS resolution for chatgpt.com: working
  • TCP/HTTPS connectivity to chatgpt.com:443: TcpTestSucceeded: True
  • Codex/ChatGPT processes are running
  • Multiple outbound HTTPS connections from Codex/ChatGPT are established
  • No evidence of a general local Internet or DNS failure

The Codex process had established HTTPS connectivity while Remote remained unavailable.

Suspected failure stage

The account/mobile side appears to know about the Windows host and pairing succeeds, but the Windows desktop Remote Connection Manager never receives/creates a connection entry (savedRemoteConnectionCount=0, discoveredConnectionCount=0, codexManagedConnectionCount=0).

This may be a Remote Control state/control-plane synchronization issue rather than a local pairing or general network failure.

Related reports

There appear to be other Windows/Android Remote reports, including issues where pairing succeeds but Remote later cannot access the host. This report includes the repeated zero-connection desktop log state and reproduction after Windows App Repair and full App Reset.

No credentials, tokens, account IDs, device IDs, or private project content are included.

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

Start with the Windows Remote Connection Manager and trace the repeated refresh, reconcile, and load log sequence described in the report. Compare the successful Android pairing with the desktop counts remaining at zero; the issue is done when a paired Android device produces a managed or discovered connection and can connect to the Windows host.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
desktop-dev, mobile-dev, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.