Codex Desktop Remote Project Picker cannot select existing Windows SSH folders

Open 💬 2 comments Opened May 19, 2026 by thor-shuang

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

OpenAI.Codex_26.513.4821.0

What subscription do you have?

enterprise

What platform is your computer?

_No response_

What issue are you seeing?

Summary

Codex Desktop Remote Connections can connect to my Windows SSH remote host successfully, but "Add remote project" cannot select an existing folder on that remote host.

The SSH connection itself works. The remote folder exists. Codex CLI is installed and runnable on the remote host. However, Codex Desktop still shows:

请选择此远程主机上的现有文件夹

<img width="530" height="593" alt="Image" src="https://github.com/user-attachments/assets/85ce1c3d-c243-491f-b406-5d6bc080f272" />

or

无法加载此文件夹

and the "Add Project" button stays disabled.

Environment

  • Local machine: Windows 10 x64, Microsoft Windows NT 10.0.19045.0
  • Local Codex Desktop: OpenAI.Codex_26.513.4821.0
  • Remote host: Windows OpenSSH Server
  • Remote connection type: SSH
  • SSH alias: home-codex
  • Remote shell: Git Bash
  • Remote Codex CLI: codex-cli 0.130.0

Remote project paths tested

I tried all of these in Codex Desktop > Add remote project:

/c/Users/20756/remote_projects/sound_real
C:/Users/20756/remote_projects/sound_real
C:/Users/20756/remote_projects
D:/code/MyItem/develop/sound
/d/code/MyItem/develop/sound

### What steps can reproduce the bug?

1. Set up a Windows machine as the remote host with OpenSSH Server enabled.
2. Configure Codex Desktop Remote Connections on another Windows machine using SSH alias `home-codex`.
3. Verify SSH works from the local terminal:

```powershell
ssh home-codex 'echo __REMOTE_OK__; hostname; whoami; pwd; printf "SHELL=%s\n" "$SHELL"; command -v codex; codex --version; ls -ld /c/Users/20756/remote_projects /c/Users/20756/remote_projects/sound_real; ls -la /c/Users/20756/remote_projects/sound_real'

### What is the expected behavior?

_No response_

### Additional information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗