Codex Desktop New remote project omits Windows remote-control host while mobile ChatGPT can control it

Open 💬 0 comments Opened Jun 30, 2026 by zhatlas

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

Controller Mac Codex Desktop: 26.623.70822 (build 4559)

Remote Windows Codex/App Server shown in device details: 0.142.4

What subscription do you have?

Not provided

What platform is your computer?

Controller machine:

Darwin 25.5.0 arm64 arm

Remote host shown in Codex Desktop device details:

Host: DESKTOP-FOA5MGG
OS / arch: Windows / x86_64
Version: 0.142.4

What issue are you seeing?

Codex Desktop on macOS can see a Windows device named Office PC under Settings > Connections > Control other devices, and the device details show it as a signed-in/connected device:

Office PC
Host: DESKTOP-FOA5MGG
OS / arch: Windows / x86_64
Version: 0.142.4
Last online: 7 min

The same Office PC is controllable from Codex inside the ChatGPT mobile app, so the account, device authorization, and remote-control backend path appear to be working.

However, when creating a new remote project in Codex Desktop on macOS, the Remote host dropdown does not include Office PC. The dropdown only shows Linux/WSL-style hosts:

WSL2            Ubuntu / x86_64
Computer Cloud  Ubuntu / x86_64
Cloud IDE       Ubuntu / x86_64

There is no visible error. The Windows remote-control host is silently omitted from the New remote project host picker, despite being listed as connected in Settings and controllable from mobile.

What steps can reproduce the bug?

  1. On a Windows PC, install/sign in to Codex Desktop and enable remote control / device connections.
  2. On a macOS machine, sign in to the same account in Codex Desktop.
  3. Open Settings > Connections > Control other devices on macOS.
  4. Confirm the Windows PC appears as a connected/signed-in device. In this repro it appears as Office PC, with details:

``text
Host: DESKTOP-FOA5MGG
OS / arch: Windows / x86_64
Version: 0.142.4
``

  1. Confirm Codex in the ChatGPT mobile app can control the same Office PC.
  2. In macOS Codex Desktop, open the New remote project dialog.
  3. Open the Remote host dropdown.
  4. Observe that Office PC is not listed, while other Ubuntu/WSL hosts are listed.

What is the expected behavior?

If a Windows remote-control host is connected, authorized, and controllable from ChatGPT mobile, Codex Desktop should either:

  1. show that host in the New remote project Remote host picker, or
  2. explicitly explain that Windows remote-control hosts cannot currently be used as remote project hosts.

The current behavior is confusing because Settings says the device is connected/available, but the project picker silently omits it.

Additional information

This does not look like a basic authorization or offline-device problem because:

  • The macOS Settings > Connections page shows Office PC as a connected/signed-in device.
  • The Office PC details modal reports recent online status.
  • The ChatGPT mobile Codex experience can control the same Office PC.
  • Other remote hosts appear in the New remote project dropdown.

The issue appears to be specific to the Desktop App New remote project host picker / project-host eligibility path for Windows remote-control devices.

Related but not identical issues found before filing:

  • #26922: iOS connected to Codex on Windows only shows local project; SSH projects missing.
  • #24271: iOS Codex remote project picker does not mirror Desktop Codex projects.
  • #24730: ChatGPT mobile does not show Codex App SSH remote projects/sessions, while Mac host can.
  • #22255 and #23445: Windows remote project picker/folder validation issues.

Those are adjacent picker/project visibility problems, but I did not find an exact duplicate for this specific direction: macOS Codex Desktop omits a Windows remote-control host from New remote project while ChatGPT mobile can control that host.

View original on GitHub ↗