Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Codex app SSH connection to native Windows host fails: app-server unix:// creates regular file and websocket closes code=1006

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

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)

Root Cause

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)

Code Example

Codex app-server websocket closed (code=1006)
RAW_BUFFERClick to expand / collapse

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 Msys
  • ssh -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.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING