Windows Codex Desktop should support SSH remote projects to Windows OpenSSH hosts

What variant of Codex are you using?

Windows Codex Desktop

What feature would you like to see?

Summary

I would like Codex Desktop on Windows to support adding a Windows Server OpenSSH host as a remote project, in the same way it supports Linux/Unix SSH hosts.

Use case

I administer several servers from a Windows PC using Codex Desktop. For Linux servers, Codex Desktop over SSH works very well. I would like the same workflow for Windows Server administration, especially IIS/app/server maintenance, without needing to RDP into the server or run Codex CLI manually over SSH.

Environment

Client:

• Windows PC
• Codex Desktop on Windows
• SSH config alias: windowsapp

Remote host:

• Windows Server
• OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2
• Codex CLI installed and signed in
• codex-cli 0.142.5
• User: myadmin
• SSH public-key authentication works
• Codex CLI works when run locally over RDP
• Codex CLI also starts over SSH

What works

From the Windows PC:

ssh windowsapp

works using public-key authentication.

This also works:

ssh windowsapp "powershell -NoProfile -Command "codex --version; pwd""

Output includes:

codex-cli 0.142.5

I also tested installing Git for Windows and making sh.exe available:

ssh windowsapp "sh -lc 'echo hello-from-sh; codex --version; pwd'"

This worked.

What fails

Adding the host as a remote project in Codex Desktop fails.

Initial failure before Git Bash:

'sh' is not recognized as an internal or external command
'[' is not recognized as an internal or external command

After installing Git Bash and adding sh.exe to PATH, the failure changed to:

/usr/bin/bash: -c: line 2: syntax error: unexpected end of file from 'if' command on line 1
'[' is not recognized as an internal or external command

After setting OpenSSH DefaultShell to Git Bash, the failure became:

socket hung up

Server-side observations:

• sshd logs show successful public-key authentication from the client
• no durable app-server process is created
• no app-server-control directory appears
• no obvious server-side crash/event is logged

Current workaround

I can use Codex CLI over SSH directly, for example:

ssh -t windowsapp "powershell -NoProfile -ExecutionPolicy Bypass -Command "Set-Location 'C:\CodexWork'; codex --sandbox danger-full-access""

This works, but it does not provide the Codex Desktop remote-project experience.

Requested improvement

Please support Windows Codex Desktop connecting to Windows OpenSSH hosts as remote projects, including:

• PowerShell/cmd-aware bootstrap rather than assuming POSIX shell semantics
• Windows path handling
• Windows-compatible app-server/socket setup
• documented supported setup for Windows Server OpenSSH hosts
• ideally support for safe sandbox modes over SSH, not only danger-full-access fallback

Why this matters

This would make Codex Desktop useful for Windows Server administration in the same way it is already useful for Linux server administration.

Additional information

_No response_