Codex app SSH connection to native Windows host fails: app-server unix:// creates regular file and websocket closes code=1006
Open 💬 1 comment Opened May 22, 2026 by beatrizya
Summary
Codex app SSH connection to a native Windows OpenSSH host authenticates and reaches the remote shell, but the remote app-server path fails. The UI reports:
Codex app-server websocket closed (code=1006)
Environment
Client:
- Codex desktop app on Windows
- Local bundled codex:
codex-cli 0.131.0-alpha.9 - OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2
Remote host:
- Windows host at
10.82.0.168 - OpenSSH server
- User:
Lab - Git Bash configured as OpenSSH
DefaultShell uname -a:MINGW64_NT-10.0-26100 bf3-qm-desktop 3.5.7-463ebcdc.x86_64 2025-03-03 17:26 UTC x86_64 Msysssh -V:OpenSSH_9.9p2, OpenSSL 3.2.4 11 Feb 2025- Remote PATH
codex:codex-cli 0.131.0 - Bundled remote Codex binary also tested:
codex-cli 0.131.0-alpha.9
What works
SSH auth and shell setup work.
What fails
Codex launches codex app-server --listen unix://. On native Windows/Git Bash, ~/.codex/app-server-control/app-server-control.sock is created as a regular zero-byte file, not a socket. Then codex app-server proxy hangs and the Codex desktop UI reports websocket closed code=1006.
Expected
Either native Windows SSH hosts should work, or Codex should detect unsupported unix:// socket behavior and show a clear message recommending WSL/Linux.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗